Date: Thu, 27 Mar 2008 20:09:33 -0400 From: "illoai@gmail.com" <illoai@gmail.com> To: "Danny Pansters" <danny@ricin.com> Cc: freebsd-stable@freebsd.org Subject: Re: Question about file system checks Message-ID: <d7195cff0803271709k471c483dq18cee69997eaaa7e@mail.gmail.com> In-Reply-To: <200803280029.08136.danny@ricin.com> References: <47EBA3AB.40307@infracaninophile.co.uk> <f9ae3129fa235b31251ec97bc12c1e78@localhost> <200803280029.08136.danny@ricin.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27/03/2008, Danny Pansters <danny@ricin.com> wrote: > On Thursday 27 March 2008 14:45:49 Marian Hettwer wrote: > > On Thu, 27 Mar 2008 13:39:55 +0000, Matthew Seaman > > > > <m.seaman@infracaninophile.co.uk> wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: RIPEMD160 > > > > > > Jared Carlson wrote: > > >> Hi I have a question about startup scripts for BSD distributions. > > >> Can you turn off the file system check that occurs every 30 boots, > > >> etc? I recall this being the case on a BSD platform, although my Mac > > >> OS X doesn't (to my knowledge) do a file system check that often at > > >> all. > > > > > > You are thinking of the Linux ext2/ext3 filesystem. > > > > Although this is OT, does anybody have a clue why ext2/ext3 filesystems > > behave like that? > > I wouldn't like to trust a filesystem which thinks a fsck is worth it, > > although it always was a clean shutdown. > > Any clue?! :) > > > ext2/3 is mounted async by default, I reckon most linux distros expect some fs > damage to occur because of that over time maybe. Or it's a relic of the days > when that was necessary, maybe it's not really necessary now anymore. It's just periodic maintenance which is nearly always set. No more necessary than running a virus check. UFS/FFS seems to do a better job of not messing up, although, if you use fat32 as the standard, ext[23] is nearly faultless as well. -- --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d7195cff0803271709k471c483dq18cee69997eaaa7e>