From owner-freebsd-arch Mon Apr 16 18:17:13 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D165C37B42C; Mon, 16 Apr 2001 18:17:09 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f3H1H8W22810; Mon, 16 Apr 2001 18:17:08 -0700 (PDT) Date: Mon, 16 Apr 2001 18:17:08 -0700 From: Alfred Perlstein To: Kirk McKusick Cc: Robert Watson , arch@FreeBSD.ORG Subject: Re: Background Fsck Message-ID: <20010416181708.P976@fw.wintelcom.net> References: <200104162353.QAA55416@beastie.mckusick.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104162353.QAA55416@beastie.mckusick.com>; from mckusick@mckusick.com on Mon, Apr 16, 2001 at 04:53:08PM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Kirk McKusick [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