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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |