I've had storage system issues (SAN / IBM VIO) on a couple of my linux systems, where the kernel has detected that the EXT3 file system has errors and has forced the block device into read-only mode.
I know that I can clear this up by rebooting (perhaps w/fsck), but I need a solution to get these file systems back into read-write mode *without rebooting*.
I want to keep error-behavior set to remount-ro, but once the storage issue has been resolved, I want the file system available for read-write again.
Nothing seems to work. The file system is read-write at the LVM level and at the blockdev level, but the kernel refuses to cooperate.
Deleted by TieFighterMod, 250 points refunded. - 5/10/2009 1:40:39 PM
# mount / -o remount,rw
mount: block device /dev/rootvg/rootlv is write-protected, mounting read-only
]# lvdisplay --ignorelockingfailure /dev/rootvg/rootlv | grep "LV Write Access"
LV Write Access read/write
# blockdev --report /dev/rootvg/rootlv
RO RA SSZ BSZ StartSec Size Device
rw 256 512 1024 0 786432 /dev/rootvg/rootlv