![]() Some operating systems, particularly Windows, may impose much shorter limits on pathnames for some operations. It is also best to avoid spaces in file and folder names, particularly when using Object Handlers.įor example, if you try to upload a file named " recipes:recent" to a Windows NTFS filesystem, the file or its contents may seem to disappear and servedat may log an error because Windows reserves the ' :' character for Alternate Data Streams.ĮxpeDat limits the total length of a file's pathname to 1024 bytes, including UTF-8 encoding. Avoid the following characters in file names: When transferring files between different platforms is is possible for a file name which is valid in one context to cause problems in another. When transferring files with Streaming Folders, the limit is approximately 2 billion files, regardless of available memory.Ĭertain characters should not be used in file and folder names because they have special meaning on some platforms. The 64-bit versions will be limited only by available RAM. On systems with at least 4 gigabytes of free RAM, this is typically about one million files for the 32-bit versions of ExpeDat Desktop or DropDat, and about eight million for movedat. The maximum number of individual files which can be transferred one-at-a-time (as opposed to Streaming) is limited by available client system memory (RAM). The total size of all files transfered per client session must be less than 16 exabytes. Individual files transferred by ExpeDat must be less than 8 exabytes each, or the maximum file size supported by the host operating system. To prevent macOS 10.10 or later from accidentally using the SMB2 protocol, and avoid an unrelated SMB3 signing bug, create or edit the file /etc/nf and place the following text at the end: You can see which SMB versions your mac is using by typing the following command in a terminal:Īs of ExpeDat 1.18D, the minimum supported macOS is 10.10 which supports SMB3. To avoid this issue under 10.9, you must mount Windows file servers using the " cifs://" URL, which forces the use of the SMB1 protocol, or use a different NAS protocol such as NFS or AFP. SMB2 was the default protocol for macOS 10.9 when mounting a Windows file server in the Finder or when using an " smb://" URL. MacOS may corrupt file data when writing to SMB2 network attached storage. In some cases, it may be desireable to serve different storage devices from separate ExpeDat hosts. To control which devices users can access, set RestrictHome and use AllowPath to limit access to approved devices. See Tech Note 0029 for guidance on tuning NAS devices for high performance.īe wary of allowing users to access arbitrary network mounts (such as with UNC paths). ![]() ![]() For best performance, ensure that all storage devices are capable of consistently reading and writing data faster than the network. This is especially noticeable when writing to network attached storage systems of differing capabilities. In extreme cases, a hung storage device may hang the entire host operating system. When writing files to multiple storage devices, poor performance by one storage device may degrade performance for other devices. Network attached storage mounts may enforce their own authentication and access controls which may restrict access by the ExpeDat server. See the Performance chapter for general guidance on storage performance. If you must use NAS, see Tech Note 0029 for guidance on tuning NAS devices for high performance. Transferring files which are stored on NAS devices may be severely limited by the speed of the legacy protocols used by those devices. Network Attached Storage Mixed Storage Performance macOS SMB2 Corruption Maximum File Sizes Memory Limitations Special Characters Maximum Path Length Windows Command Syntax Non-ASCII Characters Windows Performance Small MTU Compressed Upload Resume Drag and Drop Listing Performance File Access Conflicts Linux SMB Upload Hangs Linux SMB Permission Errors Compression Performance Compression Statistics Streaming Statistics Resume Statistics System Clock Accuracy OS Progress Symbolic Links Irregular Files Checkpoint Files "Lost" Transactions Server Restarts Mass Deletion Hierarchical Wild-Cards Windows Browser Sorting Slow Devices Write Confirmation Hardware Failure Username Case Sensitivity Filename Case Sensitivity WinSock Reset
0 Comments
Leave a Reply. |