Date: Tue, 31 Jul 2018 02:31:55 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 230220] UFS: the freezing ioctl (i.e.UFSSUSPEND) causes panic or EBUSY Message-ID: <bug-230220-227-DbfJnhv4Og@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230220-227@https.bugs.freebsd.org/bugzilla/> References: <bug-230220-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230220 --- Comment #3 from Dexuan Cui <decui@microsoft.com> --- BTW, I don't know why the file contrib/hyperv/tools/hv_vss_daemon.c (https://github.com/freebsd/freebsd/blob/master/contrib/hyperv/tools/hv_vss_daemon.c does NOT use ioctl(g_ufs_suspend_handle, UFSRESUME, ...). I found the below links: https://lists.freebsd.org/pipermail/freebsd-fs/2016-June/023447.html https://reviews.freebsd.org/D8224?id=22069 And the 2nd link says: "the filesystem gets automatically unsuspended as soon as you close the /dev/ufssuspend file descriptor." So it looks closing the /dev/ufssuspend file descriptor is equivalent to ioctl(g_ufs_suspend_handle, UFSRESUME, ...)? -- 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-230220-227-DbfJnhv4Og>