Date: Thu, 15 Jan 2009 11:20:36 -0600 From: "Rick C. Petty" <rick-freebsd2008@kiwi-computer.com> To: Brian McCann <bjmccann@gmail.com> Cc: freebsd-geom@freebsd.org Subject: Re: gvinum & gjournal Message-ID: <20090115172036.GA54383@keira.kiwi-computer.com> In-Reply-To: <2b5f066d0901150410s7dc4e97v741d5edd2a4983a9@mail.gmail.com> References: <2b5f066d0901141323j7c9a194eo4606d9769279037e@mail.gmail.com> <20090115025645.21ad2185.ota@j.email.ne.jp> <2b5f066d0901150410s7dc4e97v741d5edd2a4983a9@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 15, 2009 at 07:10:35AM -0500, Brian McCann wrote: > > I'm doing journaling so that I theoretically never have to fsck. It's You don't *have* to fsck with UFS2 either, if you're using soft updates. The only thing fsck does is free up space and inodes that are marked as used but are really not used. Since it can be done successfully in the background, I don't see much of a problem (yes it will take hours, so schedule the checks at times when you have the least I/O traffic). As far as RAM, so long as you have swap it should be fine, just adding extra time to the checks. Again you only need to run fsck if the filesystem was dirty during a reboot or crash and you need to reclaim space. I like to schedule my fscks on busy systems for 12-36 hours delay after startup. That way you don't run them after every reboot if you're experiencing problems and I like to schedule them when no one is using the system. -- Rick C. Petty
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090115172036.GA54383>