From owner-freebsd-questions Thu May 4 7:17:59 2000 Delivered-To: freebsd-questions@freebsd.org Received: from cs.Technion.AC.IL (csa.cs.technion.ac.il [132.68.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 4162037B636 for ; Thu, 4 May 2000 07:17:54 -0700 (PDT) (envelope-from nadav@cs.technion.ac.il) Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8]) by cs.Technion.AC.IL (8.9.0/8.9.0) with ESMTP id RAA12805; Thu, 4 May 2000 17:16:34 +0300 (IDT) Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.9.3/8.9.0) with SMTP id RAA07023; Thu, 4 May 2000 17:16:32 +0300 (IDT) X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs Date: Thu, 4 May 2000 17:16:32 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: kenneth@karoliussen.com Cc: freebsd-questions@freebsd.org Subject: Re: fsck and Vinum file systems In-Reply-To: <39118544.F0A4708C@activeisp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 4 May 2000, Kenneth Karoliussen wrote: > Nadav Eiron wrote: > > > > This really belongs to -questions: This has nothing to do with vinum. > > Sorry, about that. I was a glitch won't happen again :-) > > >You _asked_ for fsck not to run on this filesystem during an automatic reboot > > (that's the 0 in the last field). Replace it with a 2 (for instance) and > > all should be well. Read the man page for fstab(5). > > I just noticed that the problem has been solved in 4.0-STABLE (I'm studding the > change done from 3.4 - 4.0). > > My problem actually referred to a 3.4-STABLE system, where fsck most likely will fail > when checking a inconsistent Vinum file system. My answer is valid for 3.4 (I don't run vinum on 4.0 yet, but I'm sure it's pretty much the same). From man fstab(5) (on a 3.4 system, FWIW): [snip] ... If the sixth field is not present or is zero, a value of zero is returned and fsck(8) will assume that the filesystem does not need to be checked. In your fstab, for this filesystem, the last (sixth) field is zero. This means that fsck will _not_ check this filesystem at all during an automatic boot. This means that if it needs an fsck, mount will find that out, and will stop the boot process, demanding you to fsck in single user mode. I have a 3.4 machine with two vinum filesystems that get fsck'd just fine (with the correct entry in fstab, of course). > > /Kenneth > > On Thu, 4 May 2000, Kenneth Karoliussen wrote: > > Is there a convenient way to make fsck repair inconsistent vinum filesystems properly, > > without dropping into single modus if an improper shutdown occurs? > > > > I have the following Vinum fstab entry in my FreeBSD 3.4-STABLE system: > > /dev/vinum/vol/usr /usr ufs rw 2 0 > > > > /Kenneth > > > > > Nadav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message