Date: Wed, 01 Aug 2018 13:39:59 +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-CrwA7uKnEl@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=3D230220 --- Comment #10 from Edward Tomasz Napierala <trasz@FreeBSD.org> --- You might want to look at the tool the ffs freeze mechanism was created for: growfs(8). There is no equivalent of fsfreeze(8), because it would be inherently dangerous: you'd easily end up with a frozen machine that can only be power-cycled. With the current design you can safely ^C the utility and the writes will unfreeze. >From a big picture point of view, why is this required in the first place? = I mean, why do you need to freeze the filesystems "from the inside" instead of just pausing them in the hypervisor? --=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-230220-227-CrwA7uKnEl>