Date: Fri, 2 Jan 2004 11:17:53 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Joan Picanyol <lists-freebsd-current@biaix.org> Cc: freebsd-current@freebsd.org Subject: Re: fsck on reboot in 5.x Message-ID: <20040102111401.R57649@carver.gumbysoft.com> In-Reply-To: <20031231160538.GA42680@grummit.biaix.org> References: <20031225192817.GA14608@grummit.biaix.org> <20031230190639.B35480@carver.gumbysoft.com> <20031231160538.GA42680@grummit.biaix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 31 Dec 2003, Joan Picanyol wrote:
> [dropped dwhite from To:, I assume he doesn't need two copies]
>
> * Doug White <dwhite@gumbysoft.com> [20031231 04:02]:
> > > On a related isue, what does fsck do with fs's on vinum volumes with
> > > regard to sequential/parallel fsck'ing?
> > I'm not sure what you're asking about here. Vinum volumes are configured
> > before non-root filesystems are checked and mounted, so it would work the
> > same as non-vinum volumes.
> >From the man page:
>
> In preen mode, after pass 1 completes, all remaining file systems are
> checked, in pass number order running one process per disk drive in par-
> allel for each pass number in increasing order.
>
> What does fsck consider a "disk drive" in the following setup?
>
> [joan@iaeste-catalunya:~]0 $sudo vinum ld
> D vermell State: up /dev/ad2s2d A: 38435/74786 MB (51%)
> D verd State: up /dev/ad0s2d A: 38435/74786 MB (51%)
> [joan@iaeste-catalunya:~]0 $sudo vinum lv
> V tmp State: up Plexes: 1 Size: 5119 MB
> V std-var State: up Plexes: 2 Size: 1024 MB
> V home State: up Plexes: 2 Size: 10 GB
> V base State: up Plexes: 2 Size: 512 MB
> V package State: up Plexes: 2 Size: 1024 MB
> V apps State: up Plexes: 2 Size: 5120 MB
> V std-root State: up Plexes: 2 Size: 512 MB
> V aegee State: up Plexes: 2 Size: 15 GB
> [joan@iaeste-catalunya:~]0 $
The volumes ('V' lines) are the "disk drives" here, since each contains
its own filesystem. fsck only works on filesystems.
> Still on the fsck man page, what determines "bgfsck availability" as
> refered here?
background fsck requires that the filesystem is ufs and bgfsck has not
been disabled via a commandline flag (which gets set from rc.conf).
Don't stress bgfsck too much -- it takes care of itself. Your problem is
that the initial preen isn't getting run which usually happens if the pass
number is 0 (which means 'ignore'). Set the pass number on / to 1, the
rest of the mounted-on-boot filesystems to 2, and you should be fine.
--
Doug White | FreeBSD: The Power to Serve
dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040102111401.R57649>