strange ext3 corruption problem on 2.6.x
Quoted 3 lines · On Mon, Mar 15, 2004 at 08:59:29AM +1030, [email protected] wrote:
'r/o' by the RAID layer, presumably unbeknownst to VFS; are you *sure* that your array is still up and 'good' when you get this message?
As I said, there are no other messages, so if there is a problem (cabling, disk-i/o etc.), then the kernel doesn't know it either (usually the kernel it quite loud in this condition).
The array also comes up clean and synced. And the reiserfs partition on the same lv doesn't have any problems (wether this means that reiserfs doesn't suffer from this bug or wether reiserfs is just unable to detect it is, of course, a different question).
Signature · 7 lines
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [email protected] |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|Hi!
Quoted 7 lines
Quoted 3 lines
'r/o' by the RAID layer, presumably unbeknownst to VFS; are you *sure* that your array is still up and 'good' when you get this message?
As I said, there are no other messages, so if there is a problem (cabling, disk-i/o etc.), then the kernel doesn't know it either (usually the kernel it quite loud in this condition).
Hmm, is there way to force raid5 to check parity? Mostly "degraded" mode with all disks online. Could be usefull for cabling problems and debugging raid...
Signature · 1 line
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms