Date: Tue, 14 Mar 2006 11:20:56 -0600 From: Eric Anderson <anderson@centtech.com> To: Ensel Sharon <user@dhp.com> Cc: freebsd-fs@freebsd.org Subject: Re: please help - explanation for odd fsck times/behavior needed Message-ID: <4416FB78.5020304@centtech.com> In-Reply-To: <Pine.LNX.4.21.0603141206140.8684-100000@shell.dhp.com> References: <Pine.LNX.4.21.0603141206140.8684-100000@shell.dhp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ensel Sharon wrote: > On Tue, 14 Mar 2006, Eric Anderson wrote: > > >> 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. >> > > > Funny you should mention it, because you don't even need a large partition > to do that ... my 400 gigabyte partition (sorry folks, 400 GB is _not_ > large) requires this: > > add the line: kern.maxdsiz="1024000000" to /boot/loader.conf > > So anyway, not only are passes > 2 possibly useful, you don't even need a > big partition to have them be possibly useful ... > True - it depends mostly on number of inodes in use I believe. 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?4416FB78.5020304>