- Mac Empty Trash Locked Files
- Close_remove_share_mode Could Not Get Share Mode Lock For File
- How To Unlock Files In Windows 10
Mac Empty Trash Locked Files
I didn't want to necrobump - so I'm making this thread. But basically my question is the same as this thread:I've been trying to get my setup using more 'modern' formats and protocols. Namely - moving from writing my backups as a sparseimage to a sparsebundle. Also working on moving from AFP sharing to SMB. I've been working on this all day - and it's working (with problems). I do want to say thanks to for helping me out this morning in another thread.Anyway - the crux of my problem now is what appears to be file locking issues.
Close_remove_share_mode Could Not Get Share Mode Lock For File
With a sparsebundle format, the image is split into many smaller files called 'bands'. After I run my backup (I use Carbon Copy Cloner) - I still see 'locked' files on FreeNAS (I'm running smbstatus to see this). I've tried some of the suggestions in that thread from 2017, but I still have the issue. I can recreate the issue by browsing to the share, mounting the sparsebundle, poking around, unmounting the sparsebundle and finally unmounting/disconnecting the SMB share in Finder.
This is where the problem occurs as Finder will pop a warning that files are in use and present me with the option to 'Force eject' - which I reluctantly do.Is there any new information or solutions for this? I'm really trying to get with the times and move away from AFP - but man - having something that works without all of these issues is pretty temping to fall back on. AFP is a hell of a drug for meAlso relevant versions: Freenas 11.2-U2.1, macOS 10.14.3 (latest)Thanks in advance for any pointers.EDIT: Just found this:I don't pretend to understand everything there. But from what I can gather the vfsfruit module will 'fix some mac quirks'. Looks like that is slated to come in with some 11.3 version of FreeNAS. Is this something I could try now?
I don't want to blindly add these vfs parameters to the config. So I took some time this morning to make a test SMB share and tried the vfs modules and parameters fromDoing a CCC backup to a sparsebundle seemed to work just fine, and I could see file access in smbstatus When it was complete, there weren't stale files open/locked and I was able to cleanly unmount the share from Finder.What I did was add the vfs modules and parameters from that ticket, but I also left the defaults that were already there from FreeNAS. So my smb4.conf stanza for this test share looks like this. Code: backup-smbpath = '/mnt/bigdisk/backup-smb'printable = noveto files = /.snapshot/.windows/.mac/.zfs/writeable = yesbrowseable = yesaccess based share enum = nofruit:metadata = streamfruit:resource = streamvfs objects = catia zfsspace zfsacl fruit streamsxattrhide dot files = yesguest ok = nonfs4:mode = specialnfs4:acedup = mergenfs4:chown = truezfsacl:acesort = dontcarefruit:resource = xattrfruit:metadata = netatalkfruit:locking = netatalkfruit:encoding = privateI'd like to know the extent to which these options would be automatically set in Freenas 11.3+. I'm not quite understanding what's being said in that ticket.
How To Unlock Files In Windows 10
I'm reading it as AFP / SMB co-existence? My question is more how/when/why would these options be populated automatically? Will there be some 'Enable Mac client fixes' checkbox that will do this perhaps?
I'm trying to find a way to do this. Right now I have a script that will only allow samba to be reset by running 'smbstatus', but it isn't very reliable (shows locked files when a Windows client has mapped a share, with no file activity).Is there any way to detect when Samba has files being transferred?NOTE: Only active file transfers, not mapped clientsEDIT: Here is what my script looks like until sudo smbstatus grep 'No locked files'doecho 'Processes Running.' Sleep 5echo 'donesudo service smbd restartecho 'Restarted SMB'.