Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Sep 2001 11:03:58 +1000
From:      Greg Lehey <grog@lemis.com>
To:        "Marc G. Fournier" <scrappy@hub.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: massive file system corruption of vinum file system ...
Message-ID:  <20010914110357.A468@canberra.worldwide.lemis.com>
In-Reply-To: <20010913081123.J10290-100000@mail1.hub.org>; from scrappy@hub.org on Thu, Sep 13, 2001 at 08:15:35AM -0400
References:  <20010913081123.J10290-100000@mail1.hub.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 13 September 2001 at  8:15:35 -0400, Marc G. Fournier wrote:
> 
> Just had one of our systems that is using vinum to create a lsrge file
> system crash ... bringing the system back up, the vinum drive is so badly
> corrupted that doing an 'fsck' on the device keeps going until such a
> point that the lost+found directory has no space left ...
> 
> doing a 'mount -f' to get a look at whether its worth working at shows 1
> block used out of >8gig, so everything on it is/was lost ... so I figured
> I'd do an newfs on the file system, which results in:
> 
> demeter# newfs -v /dev/vinum/ftpmirror
> Warning: 1020 sector(s) in last cylinder unallocated
> /dev/vinum/ftpmirror:   176167940 sectors in 43010 cylinders of 1 tracks, 4096 sectors
>         86019.5MB in 2689 cyl groups (16 c/g, 32.00MB/g, 7936 i/g)
> super-block backups (for fsck -b #) at:
> write error: 176167940
> newfs: wtfs - writecombine: Undefined error: 0
> 
> I ended up having to do a 'vinum resetconfig' and 'vinum create' to get
> the newfs to work ...
> 
> The OS is from August 13th:
> 
> 	4.4-PRERELEASE #5: Mon Aug 13 15:09:31 ADT 2001
> 
> Does anyone know of any problems, from around that data, that would
> explain such a magnitude of corruption?  Its the worst I've seen to date,
> on any version of Unix I've used :(

Well, with only that information, you're really making it easy for me,
aren't you?  I've pointed to the information I need at least a dozen
times before.  In all probability a single disk didn't come back up,
and it's more than possible that this error was recoverable, but not
after you tried a newfs.  Read the man page or
http://www.vinumvm.org/vinum/how-to-debug.html and send me the info I
ask for there.

Greg
-- 
Finger grog@lemis.com for PGP public key
See complete headers for address and phone numbers

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?20010914110357.A468>