-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2009-02-02 at 17:35 +0100, Thorsten Moorhoff wrote:
Hm, ok.
I had the same problem you describe with a vmware esx, but maybe this can help you: the problem was the kernel scsi-driver in the guest (I assume your guest has also an msi-logic scsi adapter). When the host disk-system was on high traffic, the underlying guest couldn't write his journaling entries to disk in the right amount of time. Before writing nonsense to disk, the guest system decided to go read-only.
I might have what appears to be a related problem. I have an external disk, connected via usb (which uses the scsi subsystem), on this 11.0 machine, formatted as reiserfs, and it develops errors that force it to become read-only, and requires a long session of reiserfsck --rebuildtree. I see this on the log: Feb 2 02:11:45 nimrodel kernel: sd 0:0:0:0: [sda] Sense Key : No Sense [current] Feb 2 02:11:45 nimrodel kernel: Info fld=0x0 Feb 2 02:11:45 nimrodel kernel: sd 0:0:0:0: [sda] Add. Sense: No additional sense information Feb 2 02:11:45 nimrodel kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 60651 does not match to the expected one 1 Feb 2 02:11:45 nimrodel kernel: REISERFS error (device sda2): vs-5150 search_by_key: invalid format found in block 12648508. Fsck? Feb 2 02:11:45 nimrodel kernel: REISERFS (device sda2): Remounting filesystem read-only In the log I see hundred of these: Feb 2 16:54:44 nimrodel kernel: Info fld=0x0 Feb 2 16:54:44 nimrodel kernel: sd 1:0:0:0: [sda] Add. Sense: No additional sense information Feb 2 16:54:46 nimrodel kernel: sd 1:0:0:0: [sda] Sense Key : No Sense [current] Feb 2 16:54:46 nimrodel kernel: Info fld=0x0 Feb 2 16:54:46 nimrodel kernel: sd 1:0:0:0: [sda] Add. Sense: No additional sense information Feb 2 16:54:49 nimrodel kernel: sd 1:0:0:0: [sda] Sense Key : No Sense [current] Feb 2 16:54:49 nimrodel kernel: Info fld=0x0 Feb 2 16:54:49 nimrodel kernel: sd 1:0:0:0: [sda] Add. Sense: No additional sense information Feb 2 16:54:53 nimrodel kernel: sd 1:0:0:0: [sda] Sense Key : No Sense [current] Feb 2 16:54:53 nimrodel kernel: Info fld=0x0 Feb 2 16:54:53 nimrodel kernel: sd 1:0:0:0: [sda] Add. Sense: No additional sense information Feb 2 16:54:57 nimrodel kernel: sd 1:0:0:0: [sda] Sense Key : No Sense [current] Feb 2 16:54:57 nimrodel kernel: Info fld=0x0 Feb 2 16:54:57 nimrodel kernel: sd 1:0:0:0: [sda] Add. Sense: No additional sense information Feb 2 16:56:11 nimrodel kernel: sd 1:0:0:0: [sda] Sense Key : No Sense [current] Feb 2 16:56:11 nimrodel kernel: Info fld=0x0 Feb 2 16:56:11 nimrodel kernel: sd 1:0:0:0: [sda] Add. Sense: No additional sense information Feb 2 16:56:15 nimrodel kernel: sd 1:0:0:0: [sda] Sense Key : No Sense [current] Feb 2 16:56:15 nimrodel kernel: Info fld=0x0 Feb 2 16:56:15 nimrodel kernel: sd 1:0:0:0: [sda] Add. Sense: No additional sense information Feb 2 16:56:37 nimrodel kernel: sd 1:0:0:0: [sda] Sense Key : No Sense [current] Feb 2 16:56:37 nimrodel kernel: Info fld=0x0 In my case, I did not have the problem in opensuse 10.3, it apeared on 11.0. Did you fill a Bugzilla? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmHq5YACgkQtTMYHG2NR9UrIwCfcEHjxZvaiXeC5rcI78Fa7+eA c0QAnA8+Qh9uiM6sIizsAWYEgp7xy4xD =CWx+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org