xfs
[Top] [All Lists]

Re: xfs I/O error

To: Rekrutacja119 <rekrutacja119@xxxxxxxxx>
Subject: Re: xfs I/O error
From: Iustin Pop <iusty@xxxxxxxxx>
Date: Sat, 23 Feb 2008 23:08:18 +0100
Cc: xfs@xxxxxxxxxxx
In-reply-to: <2db2c6b80802231346r78d59381j49927e15f40e7ef8@mail.gmail.com>
Mail-followup-to: Rekrutacja119 <rekrutacja119@xxxxxxxxx>, xfs@xxxxxxxxxxx
References: <2db2c6b80802231346r78d59381j49927e15f40e7ef8@mail.gmail.com>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.17+20080114 (2008-01-14)
On Sat, Feb 23, 2008 at 10:46:52PM +0100, Rekrutacja119 wrote:
> hello, is there any way to force XFS to ignore I/O errors? it seems it is
> shutting down the fs when it encounters any error.
> The problem is that i can't mark badsectors, as XFS doesn't support bad
> sector marking, but i also cannot access any correct data on partition,
> because when i try to access damaged sector, the whole fs goes down.
> 
> any idea why?
> 
> i use xfsprogs 2.9.4, my xfs is array made from 3 HDs, RAID 0, and one of
> them is getting some bad sectors. i cannot replace it currently.
> 
> after i run xfs_repair on it, i was able to mount it and access the data,
> but when somebody tries to access bad data, the whole XFS goes down. i don't
> want that, i also dont have place to xfsmetadump the whole array to another
> disks.
> 
> i tried scaning whole disk with badblocks (badblocks -c 1 -s -v /dev/sdb),
> and then running dd if=/dev/zero of=/dev/sdb count=1 bs=1
> seek=NUMBER_FROM_BADBLOCKOUTPUT
> 
> but every block was written fine! (which is strange i guess), and it didnt
> help.

I'm not really sure, but the above seems wrong. badblocks has a default
block size of 1024 (-c does something else, not set the block size), and
you use that block number as an offset in bytes for dd  (because you set
bs=1).

I would recommend to try the dd again, but with bs=1024. And afterwards,
rerun badblocks and check you have no errors.

As for xfs, I don't think if it can do what you want (ignore bad
blocks), if the error is in the metadata sections.

regards,
iustin


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