Date: Wed, 5 Jun 2002 10:51:24 -0700 From: dannyman <dannyman@toldme.com> To: Chris Fedde <chris@fedde.littleton.co.us> Cc: Patrick Thomas <root@utility.clubscholarship.com>, freebsd-questions@FreeBSD.ORG Subject: Re: use of fsck -y Message-ID: <20020605105123.E16343@pianosa.catch22.org> In-Reply-To: <200206021633.g52GXXQW048693@fedde.littleton.co.us>; from chris@fedde.littleton.co.us on Sun, Jun 02, 2002 at 10:33:33AM -0600 References: <20020602071202.U18408-100000@utility.clubscholarship.com> <200206021633.g52GXXQW048693@fedde.littleton.co.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 02, 2002 at 10:33:33AM -0600, Chris Fedde wrote: > On Sun, 2 Jun 2002 07:15:08 -0700 (PDT) Patrick Thomas wrote: > +------------------ > | > BTW. softupdates might also give you some performance advantages > | > on peudo disk device filesystems. > | > | Will softupdates make fsck irrelevant ? That is, is it like journalling > | in the sense that I can cut the power and not lose anything ? Or do I > | still need to fsck after a crash ? > +------------------ > > Softupdates ensures that the filesystem is always consistent on > disk. It also reduces the number sync operations which improves > create/delete performance and read/write on small files. A hard > crash still will not mark the file system clean so a plain mount will > fail. I've not experimented much with force mounting unclean > softupdate enabled file systems. But I've never had a softupdate > file system fail fsck -p. 5.0-RC1 will let you kill a machine, and it will then reboot, mount filesystems, and fsck them in the background. -danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020605105123.E16343>