Date: Mon, 16 Apr 2001 18:17:08 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: Kirk McKusick <mckusick@mckusick.com> Cc: Robert Watson <rwatson@FreeBSD.ORG>, arch@FreeBSD.ORG Subject: Re: Background Fsck Message-ID: <20010416181708.P976@fw.wintelcom.net> In-Reply-To: <200104162353.QAA55416@beastie.mckusick.com>; from mckusick@mckusick.com on Mon, Apr 16, 2001 at 04:53:08PM -0700 References: <Pine.NEB.3.96L.1010405001328.24669L-100000@fledge.watson.org> <200104162353.QAA55416@beastie.mckusick.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Kirk McKusick <mckusick@mckusick.com> [010416 16:53] wrote: > > Only (2) seems to be a problem, and it has not proven to be an issue in > years past. If it is perceived to be a bigger problem now, a fix could be > found. A general solution would be to flock the underlying special device > as this would work for both foreground and background fsck. At the moment, > the /dev filesystem cannot handle advisory file locks, so some serious > work would be needed there first. If only background fsck is considered > to be an issue, then an flock could be held on the mount point directory. > This latter approach seems half baked to me, so I am not inclined to do it. Actually Terry Lambert has some really old patches that make flock on just about any vnode backed fd work. Do we want this? I think I can re-forward-port his delta to achieve this. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ 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?20010416181708.P976>