From owner-freebsd-current Wed Apr 4 23:53:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 0828037B43C for ; Wed, 4 Apr 2001 23:53:43 -0700 (PDT) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id IAA18476; Thu, 5 Apr 2001 08:53:40 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 14l3eF-0000sG-00 for ; Thu, 05 Apr 2001 08:53:39 +0200 Date: Thu, 5 Apr 2001 08:53:39 +0200 From: Szilveszter Adam To: current@FreeBSD.ORG Subject: Re: fstab weirdness / UPDATING Message-ID: <20010405085339.A2010@petra.hos.u-szeged.hu> Mail-Followup-To: Szilveszter Adam , current@FreeBSD.ORG References: <20010404224922.A17723@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010404224922.A17723@fw.wintelcom.net>; from bright@wintelcom.net on Wed, Apr 04, 2001 at 10:49:22PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, On Wed, Apr 04, 2001 at 10:49:22PM -0700, Alfred Perlstein wrote: > > I've had that problem on one box also -- when the boot occurs, my /var > > partition is not fsck'd. It's the second pass-two file system, which > > means that it *should* be checked :-). I suspect a nit in the recent fsck > > cleanup, so I'm CC'ing phk, whose mailbox is obviously too empty. > > I think I'm seeing the same thins... > > At boot I see a kernel printf "warning: /var was not properly > dismounted" then /var mounts. If I unmount it and fsck it it's > dirty. I saw something similar too, but did not get around to posting yet because I wanted to understand what's going on. On boot, I see only two of my partitions being reported as clean, and not the others. After this, all of them are mounted allright. (They happen to be ad0s1a and ad0s1f don't know why...) I don't know if it causes filesystem corruption, because it is my policy to always 'boot -s' upon unclean shutdown and fsck all partitions manually. (In fact I just did it again because X has a tendency to freeze the machine off and on for unknown reasons... maybe related?) If this is an fsck problem, then I figured there was no big problem if your previous shutdown was clean... am I right? Or maybe there is a problem with shutdown too that fsck simply doesn't notice? Brrr...:-) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message