Date: Sat, 10 Mar 2018 14:27:48 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 226499] Partial system freeze via ZFS rename and possible other operations Message-ID: <bug-226499-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226499 Bug ID: 226499 Summary: Partial system freeze via ZFS rename and possible other operations Product: Base System Version: 11.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: paul.g.webster@googlemail.com It is possible to create a partial system freeze with zfs by renaming an ac= tive mountpoint; in my case I had a vdev mounted within bhyve. When I accidentally did a: 665 19:39 zfs rename zroot/venv/store/paul.daemon.space-extended zroot/venv/store/services.daemon.space-extended The zfs command froze and refuse to return (even via kill -9) the bhyve vm = will refuse to exit, and the system will not reboot; it will get stuck trying to unmount filesystems. Likewise if you open up another terminal and try any command via 'zfs' it w= ill end up in the frozen state, (actual state reported in top is: tx->tx) This is a partial freeze because all other system operations will continue normally. It appears though have not investigated earlier, that rename does not check= a dataset is bust like destroy does, so then gets stuck in some sort of lock waiting for it to become available in the meantime nothing else can do anything, including any process that is actually locking whatever you are trying to rename. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-226499-8>