Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Feb 2003 12:37:02 -0500
From:      Bill Moran <wmoran@potentialtech.com>
To:        Heinrich Rebehn <rebehn@ant.uni-bremen.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: fsck takes very long after crash/reset
Message-ID:  <3E4A863E.2030801@potentialtech.com>
References:  <3E4A5B77.5080103@ant.uni-bremen.de>

next in thread | previous in thread | raw e-mail | index | archive | help
Heinrich Rebehn wrote:
> Hi list,
> 
> 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.

I would expect that from 300G

> Most partitions, especially the large ones are mounted with soft-updates.

Good.

> 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.

Sounds to me like you need to address your hardware or environmental problems.
If your system is needing hard-booted that often, you'll benefit from fixing
the cause of the hard-booting more than from a journalling fs.

> My collegues ask me why i don't use a journalling file system, but 
> FreeBSD doesn't seem to provide any.

Collegues are like that.  No matter what you do, they'll ask why you didn't
do the thing that they think will save the day.

The journalling fs issue seems to come up on this list every few months.
Search the archives and you'll find a lot of information on it compared
to soft updates.

> Is there any way to speed up the fsck? 20 minutes really is too long!

FreeBSD 5.0 has background fsck, which seems to work very well in the
limited tests I've done.  fscking doesn't interrupt the boot process at
all.  However, 5.0 isn't considered production quality yet, so you can
only really consider it for the near future.

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com


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?3E4A863E.2030801>