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: Sun, 24 Feb 2008 10:01:06 +0100
Cc: xfs@xxxxxxxxxxx
In-reply-to: <2db2c6b80802231414m38f70795n7f24fea1a40195df@mail.gmail.com>
Mail-followup-to: Rekrutacja119 <rekrutacja119@xxxxxxxxx>, xfs@xxxxxxxxxxx
References: <2db2c6b80802231346r78d59381j49927e15f40e7ef8@mail.gmail.com> <20080223220818.GC27124@teal.hq.k1024.org> <2db2c6b80802231414m38f70795n7f24fea1a40195df@mail.gmail.com>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.17+20080114 (2008-01-14)
On Sat, Feb 23, 2008 at 11:14:32PM +0100, Rekrutacja119 wrote:
> so i should use the list i got from badblocks with dd but with bs=1024? are
> you sure? i'm not sure what is my block size, but xfs_info says this:
the block size of the filesystem has no relation to the block size
badblocks uses in checking the block device.
> 
[...]
> 
> i think i made it with 4K stack size ... well anyways, i should use the list
> i got earlier and just try dd but with bs=1024... ? don't want to erase more
> than i have to. (i want to do it so i can smartctl -t offline /dev/sdb then,
> so maybe it will somehow see that these blocks are broken and mark them)

I don't understand what do you want to do with smartctl at all. How
would offlining the disk would help?

Again, I would:
  - take the block list given by badblocks
  - verify that each block can't be read  first via dd if=/dev/...
    of=/dev/null bs=1024 count=1 seek=NUMBER_FROM_BADBLOCK
  - if confirmed that you got the right 'bad' blocks, use that for dd
    with bs=1024 to write zeroes over them

As Eric confirmed, you probably already destroyed some good data on the
drive.

regards,
iustin


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