![]() ![]() If indexing was the only issue, we would expect that, if the contents of the disk have been successfully index, then only minor indexing would be needed moving forward. But the indexing seems to go on forever (at least, a long time). Let’s take a look at the version control settings: So we need to consider there is more than one thing contributing to the high disk IO. You can see the version control is enabled. This defaulted to 32 (the maximum) but as a test, I downgraded it to just 3. It didn’t seem to make any different to the high resource utilization. In other words, 1 version retention versus 32 version retention doesn’t seem to make a different. Here’s where I theories that the issue is a combination of enabling version control at the same time as enabling indexing on the same data. To demonstrate my theory, I have disabled version control as you can see here: The data is changing throughout the day, versions are being added and removed (entering and leaving the retention limits) and that’s causing indexing to continue for ever. I revisited the resource manager to validate my change. In fact, the re-indexing process continues to use high disk IO. I only disabled the version control, not the index process. You can see the indexing status is still “Indexing”. So the next thing to do is disable indexing. I SSH’d into the NAS, located the process ID for “fileindexd” and killed it. Take a look at the result in the screenshot below: Actually, I had to move that program asside and then kill it – to prevent it from auto restarting. But it’s not the right way to achieve it. Obviously disabling a process by moving it and killing it is not the right way. If we can solve why the 3 folders show zero bytes over the network, the failure to copy may well go away too.But it’s compounded by having to deal with version control. This is not real surprising, 'cause yesterday I used Migration Assistant to copy virtually everything from the Pro to the Air. Permissions on Air ~: Desktop 770, Pictures 700, Public 775.Įxactly the same things happen in the opposite direction, from the Air to the Pro. If I try to drop a file (from the Pro desktop) into the Air Desktop, I get the message 'Items can't be copied to "Desktop" because you don't have permission to read them.' I can drop the same file successfully into either Air ~/Pictures or Air ~/Public. Viewing ~ on the Air shows reasonable non-zero sizes for these folders. ![]() Three folders in Air ~ are shown as having Zero bytes: Desktop, Documents, and Downloads. I open a Finder window with a Sidebar, and click on the MacBook Air in the Sidebar. Any suggestions would be very helpful! :)Ĭopying files from desktop to desktop I want to copy files from the Desktop of our MacBook Pro 15" 2016 macOS Monterey 12.6.1 to the Desktop on our MacBook Air M2 2022 macOS Ventura 13.0.1. The only thing changing is MacOS and Pages updates. I haven't tested with other apps like Numbers so can't say if affects them too, but the Mac in general can access the paths via Finder and I've been working with this setup for years. Synology NAS DSM 6.2.3-25426 Update 3 (latest update) I can't see any errors being logged on the NAS. If I save the document to my (iCloud) desktop, I can then move it manually into the share via Finder, but then it can't be autosaved if I open it in Pages again. I can create, modify and delete files from the command line in the same path. I've checked permissions on every folder in the path from the root of the share to the document destination and my own userid had read/write permission according to Finder. If I open a document or begin a new one and then try to save it or duplicate it to a shared folder on my Synology NAS I get an error stating "The document could not be saved". I've seen some discussion about similar issues, but so far haven't found a working solution. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |