Date: Thu, 5 Apr 2001 00:50:27 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Kirk McKusick <mckusick@mckusick.com> Cc: arch@freebsd.org Subject: Re: Background Fsck Message-ID: <Pine.NEB.3.96L.1010405001328.24669L-100000@fledge.watson.org> In-Reply-To: <200104012342.QAA19845@beastie.mckusick.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Kirk, Another usability question. Was wondering about the possibility of multiple background fsck's getting started at a time, et al, possibly due to bad behavior by the user. Can the user get shot in the foot in the following situations: 1) They unmount a file system during a background fsck -- not all that unlikely. (Assuming that fsck keeps a file open for use with the sysctl, or possibly eventually vfsop, a non-forcible unmount should get EBUSY, but not sure what a forcible unmount will do). 2) They start a second background fsck running at the same time as the first. 3) They perform a remount, possibly changing between read-only and read-write. In some of these, it may be OK for the user to be shot in the foot, but it might be worth considering strategies to prevent foot-shooting, especially in the case of remount situations. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1010405001328.24669L-100000>