Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 08 Aug 1999 23:04:15 +0100
From:      David Malone <dwmalone@maths.tcd.ie>
To:        Tom <tom@uniserve.com>
Cc:        David Malone <dwmalone@maths.tcd.ie>, Morgan Davis <mdavis@cts.com>, freebsd-stable@freebsd.org, dwmalone@maths.tcd.ie
Subject:   Re: Removing files in /lost+found causes panic 
Message-ID:   <199908082304.aa22521@salmon.maths.tcd.ie>
In-Reply-To: Your message of "Sun, 08 Aug 1999 14:50:13 PDT." <Pine.BSF.4.02A.9908081448001.29629-100000@shell.uniserve.ca> 

next in thread | previous in thread | raw e-mail | index | archive | help
> > I've definitely come up with times where:
> > 
> > 1) fsck checks the filesystem and gives it the OK, but it isn't.
> 
>   Yes, but is this a -p", which only does a partial check?  If so, that
> may be what it is supposed to do.

No.

>   A lot of these sound like hardware.  Some drives, especially IDE, will
> just corrupt themselves.  Turing off multi-block mode can somtimes help.
> I have a Maxtor IDE drive (8.4GB) that I can not use with FreeBSD's
> multi-block mode, as data will be corrupted and fsck will always report
> errors.

Nothing wrong with the hardware. The first time I had this trouble
was when there was a new/revised ahc driver, which sometimes locked
up one scsi bus preventing access to one half of a ccd array. Justin
fixed stuff in the driver and it's been happy as larry ever since.
The filesystem was definitely left in a state that fsck couldn't
deal with (probably because some of the writes were still making it
to the other disk?)

The most recent time I was dump/restoring 3x4GB filesystems onto
3x9GB softupdates filesystems over the network and the machine died
16 minutes before it was done. The target drives are all recent
revision Quantum Atlases connected to two Adaptec SCSI controlers.
These disks weren't striped, one filesystem per disk. I have two
people who watched do about 5 fsck's on one of the disks and it asked
me the same things every time after the first. Every time since we've
had no trouble with corruption.

(We did have one weird problem where 4GB of disk space vanished wile
using softupdates over NFS - it didn't show up with quot or du, and
even persisted across reboots and fscking. Turning off soft updates
and fscking reclaimed it I think).

	David.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi? <199908082304.aa22521>