I'd start by uninstalling sophos. Antivirus on the mac are useless and the cause oc all sorts of trouble. To fix it, we’re going to need to reformat the flash drive. That’s done by finding the “Disk Utility” program that’s included with Mac OS X in the “Utilities” folder within the “Applications” folder. It looks like this: Launch it and you’ll see a list of all drives and devices hooked up to your system: Be careful here.
Set my folders free! Earlier this year we received a number of reports from users that were unable to delete, move or rename documents on a new file share. Eventually we were able to narrow it down enough to be able to consistently duplicate what they were seeing.
It appears the SMB client in (10.11, 10.12 and possibly others) is overly aggressive with file locks. Here is a movie of the bug in action.
Many of the Mac administrators we reached out to for confirmation claimed they didn’t see it, until they followed our steps. Hello Chris: We’ll need to know the model number, configuration and current firmware version of the Synology box. And if you are willing, can you grab a packet capture and smb debug logs? If so, you can directly contact me on MacAdmin slack and send me the 1. Mount an SMB share, then dismount it 2.
What I have tried so far: • Resetting the permissions on both of the mailboxes. Outlook 206 for mac wont open. I deleted the security group permissions on both mailboxes, applied the change, then waited a bit and gave the permissions back.
Enable SMB debug logging: sudo sysctl -w net.smb.fs.loglevel=15 3. Start a packet capture, replacing BSDName with the interface you are using (en0, en1 etc) sudo tcpdump -i BSDname -s 0 -B 524288 -w ~/Desktop/56.moverename.pcap Note: “-s 0” includes a zero, not the letter O.
When prompted for a password, enter the one for your administrator account. (More info in this kb) Capture a packet trace using Terminal on your Mac 4. Mount the SMB share and reproduce the issue 5. Unmount the share and stop the packet capture Control-C •. Hello Paul: I had a few questions regarding the behavior on 10.13: 1.
Does terminal work when Finder fails? What about a 3rd party Finder alternative, such as Pathfinder? Did Synology offer any advice? Can you try disabling notifications in the nsmb.conf file and let me know if Finder’s behavior changes? (Don’t grab the debug data with this change enabled) sudo -s echo “[default]” > /etc/nsmb.conf echo “notify_off=yes” >> /etc/nsmb.conf You can delete the /etc/nsmb.conf file to revert to standard behavior. Really great stuff you have here. I am able to reproduce this bug on MacOSX 10.13 High Sierra on a Synology DSM416 running DSM 6.1.4-15217.
I have submitted a support ticket with Synology yesterday and am still waiting to hear back. I did try that last step in the comment reply to Paul Major, but have not tried terminal or a 3rd party finder alternative.
For terminal, do you want all of the folder operations (creating folder A/B/C, etc) done through terminal or just the renaming step? I also have a.pcap file from the operation but I haven’t been able to properly parse it yet. Thanks again for the super detailed explanation and reproduction steps. Hello, We’ve also been having the same issues. Renaming files, Moving files, etc. And are currently running on High Sierra. It was the same on all previous versions.
We run on an smb server and have tried ntfs servers as well and same issue. Also, have issues using adobe illustrator, saving a file. Then if I go into the file and modify it, save it. Go back into it, the second save session will not be saved and in fact shows as the original. The only fix i found for this was to do a save as every time and save over the previous versions.
The big issue for us though is the file renaming and password required, enter the password, and still will not let us rename. It gets to the point we have to create a new folder and drag everything into the properly named new folderthen delete the unwanted version. It’s irritating. @Richard Glaser – I’m still seeing this issue with macOS High Sierra 10.13.1 and 10.13.2 – it did look like it was initially fixed in 10.13, and the issue was definitely better, however now with more heavy use and newer updates, we’re back where we were before. The server is Windows Server 2016.
The symptoms are most apparent when we go into the Computer Management > Shared Folders > Open Files Even on a small network (10-20 workstations) there will often be thousands and thousands of open files, all open in Read mode. These files opened in Read only mode are not an issue on a server running a Unix-type operating system. Unix is able to move, rename and delete files that are opened with a read-only file handle. Windows on the other hand won’t do anything to any file with an open file handle. You can’t rename it, you can’t move it, you can’t delete it.