Re: xfs I/O error

[Rekrutacja119 <rekrutacja119@xxxxxxxxx>]

smartctl -t offline is i think scheduling a SMART test

i will try what you say, but there is no way to force XFS to not unmount
filesystem if it finds out I/O error?

also, i didnt edit any info, it was just all i got from messages log

2008/2/24, Iustin Pop <iusty@xxxxxxxxx>:
>
> 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
>


[[HTML alternate version deleted]]