NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MacOS directories incomplete
My network is small with only Macs connected. It accesses the ReadyNAS via SMB. One directory has about 16K files and/or folders. Often when I open this directory only some of the folders show up in ...
If you've read this thread, you'll see that I’ve had an ongoing issue with my all-Mac network. Very frequently the listing for a 2.7TB directory on a 4.25TB share is not accurate when first displayed. It may take anywhere from seconds to even five or more minutes for the directory to magically refresh itself with complete information and display all the directories.
Several people have responded with suggestions that I’ve tried but nothing seems to have worked. One post implied that the directory might simply be too large for the combination of MacOS and the Netgear Firmware to handle.
So, I’m wondering if converting that one directory to be a separate share might ameliorate the problem.
Any input on this would be helpful.
Then, if I decide to make the change, how do I convert a subdirectory on a share to become a new share?
Thanks for any input.
I'd think that the issue would more likely related to the way the files/folders are organized. Folders or subfolders that have a lot of files will have slower browsing than smaller folders. For example, if you had 100 folders of 100 files each , you'd get faster performance than 10000 files in the main folder. So maybe look at that?
Blues11 wrote:
Then, if I decide to make the change, how do I convert a subdirectory on a share to become a new share?
There's no way to directly convert it. You need to create the share, copy the subdirectory to it, and then delete it in the source share.
If you are using ssh for the copying, then you can use the --reflink option to speed up the copying. Note that each share is it's own btrfs subvolume, so moving files will take about the same time as copy/delete (unless you use --reflink).
Thanks for the quick reply.
The large subdirectory has about 1,400 folders. In each directory there are generally fewer than 10 or 15 files, one or two of which are in the range of a GB. Do you think dividing that directory into two would have a beneficial effect?
Given that the server has 5TB free, would there be a problem with copying 2.7TB to that space, leaving only 2.3TB free? Of course, once it would be completed the original 2.7TB would be deleted, but would that be too much stress on it?
Once again, thank you.
Blues11 wrote:
The large subdirectory has about 1,400 folders. In each directory there are generally fewer than 10 or 15 files, one or two of which are in the range of a GB. Do you think dividing that directory into two would have a beneficial effect?
Subdividing the large subdirectories should have some effect, so I would try that.
Blues11 wrote:
Given that the server has 5TB free, would there be a problem with copying 2.7TB to that space, leaving only 2.3TB free?
If you use --reflink then the copy would be sharing the data blocks from the original - so there would be no change in free space.
If you don't do that, then you might need to delete snapshots on the source share after you delete the files there, in order to get the free space back.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
