Date: Tue, 14 Mar 2006 11:04:39 -0600 From: Eric Anderson <anderson@centtech.com> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: freebsd-fs@freebsd.org, Ensel Sharon <user@dhp.com> Subject: Re: please help - explanation for odd fsck times/behavior needed Message-ID: <4416F7A7.90800@centtech.com> In-Reply-To: <86slpldkyf.fsf@xps.des.no> References: <Pine.LNX.4.21.0603141059060.8684-100000@shell.dhp.com> <4416EF6A.3020201@centtech.com> <86wtexdlcg.fsf@xps.des.no> <4416F448.6060602@centtech.com> <86slpldkyf.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav wrote: > Eric Anderson <anderson@centtech.com> writes: > >> Ok, thanks for the insight. Someone with a commit wand should wave >> it over fsck(8): >> > > No, the man page is correct. There's just no point in using more than > two passes unless you have so little memory that fsck starts swapping. > You'll notice that sysinstall puts everything except / in pass 2 in > the fstab it generates when you install. > Or you have such large partitions, that you need the entire amount of memory to fsck a single filesystem at all. While we're on this topic, my fsck's never seem to want to swap, they die with an error (can't recall the error), to get around it I set maxdsiz to a huge number (3gb-ish). Setting maxdsiz any higher makes the machine not boot (can't run init). Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4416F7A7.90800>