[Bug 267258] New: kernel remounts root filesystem (ext3) readonly while installing cron security update patch
https://bugzilla.novell.com/show_bug.cgi?id=267258 Summary: kernel remounts root filesystem (ext3) readonly while installing cron security update patch Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: openSUSE 10.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: adrie.voesenek@planet.nl QAContact: qa@suse.de While using opensuseupdater (system in init 5 mode) to install cron security update version 3092-0 the kernel remounts the root filesystem (ext3) readonly. This is repeatable after clean reboot (85% of root fs = 3.2 GB is free) . The following 2 lines appear in /var/log/messages : Apr 20 22:35:25 avosys64 kernel: attempt to access beyond end of device Apr 20 22:35:25 avosys64 kernel: hda10: rw=0, want=17179869192, limit=8385867 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267258 ------- Comment #1 from suse-beta@cboltz.de 2007-04-23 16:50 MST ------- Please run fsck on your root partition from a recovery system, there's probably an error in your filesystem. I doubt this is directly related to the cron patch (but you never know, of course.) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267258 ------- Comment #2 from jeffm@novell.com 2007-04-24 06:13 MST ------- Thanks, Christian. This is almost certainly file system corruption entirely unrelated to the package update. It's likely something was broken with your file system and the package update just happened to touch it. If you scroll up your log, you'll probably see something about an ext3 error taking the file system read only. Either way, the correct solution is to fsck. On commodity hardware, it's awfully tough to track down where corruption could be introduced. It could be bad RAM, a bad cable, bad disk, anything really. Some disks even flush out partial sectors when they are powered off. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=267258 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #3 from gregkh@novell.com 2007-05-03 21:51 MST ------- Closing this based on the previous comment -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com