xfs
[Top] [All Lists]

Re: XFS bad block recording?

To: Seth Mos <knuffie@xxxxxxxxx>
Subject: Re: XFS bad block recording?
From: Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Date: 04 Sep 2002 13:56:11 -0500
Cc: dbarber@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx
In-reply-to: <4.3.2.7.2.20020904204331.02e58070@pop.xs4all.nl>
Organization: Coremetrics, Inc.
References: <4.3.2.7.2.20020904204331.02e58070@pop.xs4all.nl>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Wed, 2002-09-04 at 13:44, Seth Mos wrote:
> At 14:36 4-9-2002 -0400, dbarber@xxxxxxxxxxxxxxx wrote:
> >Is there a way mark the bad blocks on the hard drive while mkfs'ing
> the
> >drive?  Or another tool to mark bad blocks on a live filesystem? 
> Just
> >curious.
> 
> Nope. XFS automatiically bails out on a IO error and umounts the
> filesystem 
> to prevent further damage.


Hrrmm....Something really bad happened then with my system. We had/have
lots of IO errors on one host, now XFS can't replay the logs, mount
segfaults. I don't think there's physical corruption, the disks are
really new, but were working fine before, and after dumping the logs,
things are good. I've got V1 logs though, dunno if that makes a
difference. 

One of the HBAs or GBICs went bellyup on us, but XFS didn't shut-down.
Now I can't mount. I don't want to dump the logs, anyone have any ideas?

> Cheers
> 
> --
> Seth
> It might just be your lucky day, if you only knew.
-- 
Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Coremetrics, Inc.


<Prev in Thread] Current Thread [Next in Thread>