>Hi all,
>
>Just now, an LVM (dm-0) volume on my FC5 system suddenly indicated
>that it was "read-only". A look at dmesg revealed some kind of I/O
>error on one of the SATA drives (sdd):
>
>[...]
>ata4: status=0xd0 { Busy }
>sd 3:0:0:0: SCSI error: return code = 0x8000002
>sdd: Current: sense key: Aborted Command
> Additional sense: Scsi parity error
>Info fld=0x43d41bf
>end_request: I/O error, dev sdd, sector 71123391
>EXT3-fs error (device dm-0): read_block_bitmap: Cannot read block
>bitmap - block_group = 2656, block_bitmap = 87031808
>Aborting journal on device dm-0.
>ext3_abort called.
>EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal
>Remounting filesystem read-only
>EXT3-fs error (device dm-0) in ext3_prepare_write: IO failure
>ata4: command 0xb0 timeout, stat 0xd0 host_stat 0x0
>ata4: status=0xd0 { Busy }
>[...]
>
>I've never seen this before. I unmounted and remounted it, and it
>seems to be working ok -- for now. Anyone know what is going on here?
I would suggest you back this disk/volume up, if you havent already
done so. You have had a disk error during an attempt to read the
bitmap data on the LVM, and the system decided it was too risky
to permit further writes to this disk.
Did you fsck the volume before re-mounting it?
Cheers,
Terry.
