Accessing a disk share takes FUSE out of the equation, and should hopefully fix this problem moving forward. So once I work out how I want to migrate the data from my array, I will be creating a pool (maybe multiple) for my array disks, which will then be surfaced as a disk share. Now at the moment because my array is still set up in the old traditional xfs (6.11.x and before, without pool functionality) I only get each disk surfaced as a share, not the pool of disks itself. What this tells us is that there is something in FUSE that is causing Mac SMB to bug out. Next is to work out how I am going to migrate my array to ZFS.Īnyway, during this I also decided to test out Disk Shares, I have never used them before (except for the cache pools), and wouldn't you know it, when accessing a disk share from Macs over SMB is instant, same as windows. I have only changed my general cache, docker pool, and VM pool which are on SSD media over to ZFS. This didn't result in any changes to the Mac SMB issue, however I am in a much better place using ZFS instead of XFS for my pools. Keen to get some insight from people and maybe even the devs as to why SMB seems to be troublesome on UnRAID for just an update on my issue, I recently started migrating from XFS to ZFS. The key here is the Macbook M2 is not affected, the Mac Mini's work fine with SMB on TrueNAS, so something in UnRAID is not quite right. However, the Macbook M2 working properly blows that theory out of the water. I have tried all sorts of different SMB config options etc, nothing works. This issue has been going on Unraid for as long as I can remember, and until I got my Macbook M2 recently, I just figured that was something I would just have to deal with using Mac with UnRAID. I have set up the TrueNAS SMB shares to be the same as the UnRAID SMB shares for making troubleshooting more accurate. I also have a TrueNAS box, so to throw another spanner in the works, the Mac Mini devices do not have any issues accessing SMB shares on the TrueNAS box. If I use SSH on the Mac Mini devices, its a lot faster, however still not like the M2 or the Windows machines, only achieving around 40MB/s transfer speed. Windows 10 machines also have no issues with the same SMB shares and max out the connection. I can copy files to and from, and it maxes out the connection. I can access all of the same unraid SMB shares via ethernet or wireless and they load instantly. So to make things more confusing, the Macbook M2 does not have this issue at all. Created brand new test shares with test data Tested iperf from both macs to unraid - maxes out gigbit connection around 975MB/s, so its not a connection issue Copy any files whether it be big single files or lots of small files, goes at around 1MB/s, when it should be around 80MB/s ![]() ![]() Loading any SMB share takes forever, regardless of how many folders and files are in the share Is NFS also affected: Sort of, no where near as bad as SMB Nothing fancy, not taxing the hardware at allĪll machines connected to network via Ethernet & Wireless Wireless: Nothing fancy, standard N & AC wifi Switch: Standard Gigabit Managed switch, no fancy config I'm going to break it down as simply as I can. So please don't lash out for a new post about it lol □' Nowwwwww I already know there have been a number of threads already about this, however this problem seems to really have no solid answer or solution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |