https://bugzilla.novell.com/show_bug.cgi?id=662252 https://bugzilla.novell.com/show_bug.cgi?id=662252#c0 Summary: warning (device sda2): clm-6006 reiserfs_dirty_inode: writing inode 273081 on readonly FS Classification: openSUSE Product: openSUSE 11.4 Version: Milestone 5 of 6 Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: doiggl@velocitynet.com.au QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20101124 SUSE/2.0.11-1.3 SeaMonkey/2.0.11 This may not affect anyone else because im using a custom kernel [1]. But thought a report may come in handy. Boot with custom kernel Run zypper up and in the process one filesystem would turn from read/write into a read only filesystem. [1] https://build.opensuse.org/package/show?package=kernel-reiser4&project=home%3Adoiggl Reproducible: Always Steps to Reproduce: 1. zypper up 2. file system would set to read only Actual Results: file system would set to read only. # dmesg [ 444.524395] packagekitd[3145] trap int3 ip:7fcbd0db8739 sp:7fcbca0953e0 error:0 [19570.162049] REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 [19570.162056] REISERFS error (device sda2): vs-5150 search_by_key: invalid format found in block 493146. Fsck? [19570.162060] REISERFS (device sda2): Remounting filesystem read-only [19570.162065] REISERFS error (device sda2): vs-13050 reiserfs_update_sd_size: i/o failure occurred trying to update [3896 98976 0x0 SD] stat data [19570.162072] REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 [19570.162076] REISERFS error (device sda2): vs-5150 search_by_key: invalid format found in block 493146. Fsck? [19570.162080] REISERFS error (device sda2): vs-13050 reiserfs_update_sd_size: i/o failure occurred trying to update [3896 98976 0x0 SD] stat data [19570.162225] REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 [19570.162229] REISERFS error (device sda2): vs-5150 search_by_key: invalid format found in block 493146. Fsck? [19570.162233] REISERFS error (device sda2): vs-13050 reiserfs_update_sd_size: i/o failure occurred trying to update [3896 98976 0x0 SD] stat data [19657.244713] REISERFS warning (device sda2): clm-6006 reiserfs_dirty_inode: writing inode 273081 on readonly FS [19657.244782] REISERFS warning (device sda2): clm-6006 reiserfs_dirty_inode: writing inode 273081 on readonly FS [19777.245123] REISERFS warning (device sda2): clm-6006 reiserfs_dirty_inode: writing inode 273081 on readonly FS [19777.245193] REISERFS warning (device sda2): clm-6006 reiserfs_dirty_inode: writing inode 273081 on readonly FS [19897.245529] REISERFS warning (device sda2): clm-6006 reiserfs_dirty_inode: writing inode 273081 on readonly FS [19897.245600] REISERFS warning (device sda2): clm-6006 reiserfs_dirty_inode: writing inode 273081 on readonly FS [19921.750948] REISERFS warning (device sda2): clm-6006 reiserfs_dirty_inode: writing inode 278730 on readonly FS [20017.242367] REISERFS warning (device sda2): clm-6006 reiserfs_dirty_inode: writing inode 273081 on readonly FS [20017.242437] REISERFS warning (device sda2): clm-6006 reiserfs_dirty_inode: writing inode 273081 on readonly FS [20038.956616] type=1400 audit(1294146601.839:182): apparmor="DENIED" operation="change_hat" info="unconfined" error=-1 pid=1101 comm="cron" [20038.956654] type=1400 audit(1294146601.839:183): apparmor="DENIED" operation="change_hat" info="unconfined" error=-1 pid=1101 comm="cron" Expected Results: stay read/write Nothing needs to be done since im not using a supported configuration so just add any of your thoughts about any workarounds then close it. I restarted pc and filesystem is read/write mode I thought the sequence of events to trigger the event was very odd. It is a reproducable event. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.