I copied a file to a cifs drive and instinctively ran a sync on it, which hung indefinitely. Strangely, I could successfully unmount/remount the drive without issues, making me think that the drive simply didn’t respond to the sync call properly. It looks like the file is not growing, so the copy was successful (about the right size too).
This sync process is still hanging, and ignoring
kill -9. I don’t want to reboot the machine as it’s a server.
Is there any way to coerce sync into thinking it’s done? Is it normal for a cifs drive to behave this way?
EDIT: The host (running the sync) is Ubuntu 16.04. I don’t know how to determine the SMB/cifs OS but I have a feeling it’s windows since the drive was originally for windows users.
I left it over the weekend, and upon returning (reattaching to tmux), it’s still hanging
Journalctl is eating CPU, and giving 1000’s of the following message per second:
Apr 08 08:14:49 [Server name] audit: AVC apparmor="DENIED" operation="recvmsg" profile="snap.canonical-livepatcchd" pid=855 comm="canonical-livep" family="netlink" sock_type="raw" protocol=15 requested_mask="receive" denied_mask="receive"