Date: Thu, 13 Feb 2003 02:45:06 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Heinrich Rebehn <rebehn@ant.uni-bremen.de> Cc: Bill Moran <wmoran@potentialtech.com>, freebsd-questions@FreeBSD.org Subject: Re: fsck takes very long after crash/reset Message-ID: <20030213004506.GA1355@gothmog.gr> In-Reply-To: <3E4A8EF5.1070308@ant.uni-bremen.de> References: <3E4A5B77.5080103@ant.uni-bremen.de> <3E4A863E.2030801@potentialtech.com> <3E4A8EF5.1070308@ant.uni-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2003-02-12 19:14, Heinrich Rebehn <rebehn@ant.uni-bremen.de> wrote: >Bill Moran wrote: >>Heinrich Rebehn wrote: >>>I operate a FreeBSD server with a 300GB Raid. This morning i had to >>>hard reset it and when booting, fsck took some 20 minutes. >>>[...] >>>Also, some weeks ago, we had missing files after a crash/fsck. >> >>Soft-updates will do that if the system crashes in the middle of >>writes. > > I have read several times that soft updates ensure that the fs is > always in a consistent state? When a file isn't fully written on the hard disk, a "consistent state" of the filesystem is one that doesn't include half-finished updates. What would you prefer? A half-finished file that possibly includes garbage, or a consistent filesystem? 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?20030213004506.GA1355>