[Bug 405264] New: ext3 turned into ext2 with root on lvm on raid0
https://bugzilla.novell.com/show_bug.cgi?id=405264 Summary: ext3 turned into ext2 with root on lvm on raid0 Product: openSUSE 11.0 Version: Final Platform: PowerPC OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: olh@novell.com QAContact: qa@suse.de Found By: --- hurtleberry, pSeries JS20 8842-21X I have installed ext3 root on lvm on raid0 over two ide disks after reboot: doing fast boot Creating device nodes with udev udevd-event[205]: node_symlink: device node '/dev/mapper/control' already exists, link to '/dev/device-mapper' will not overwrite it blogd: can not open pty/tty pair: No such file or directory mdadm: device 1 in /dev/md0 has wrong state in superblock, but /dev/sda2 seems ok mdadm: /dev/md0 has been started with 2 drives. 3 logical volume(s) in volume group "system_hurtleberry" now active 3 logical volume(s) in volume group "system_hurtleberry" now active Waiting for device /dev/system_hurtleberry/root to appear: ok fsck 1.40.8 (13-Mar-2008) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/system_hurtleberry/root hurtleberry_root: Superblock has an invalid ext3 journal (inode 8). CLEARED. *** ext3 journal has been deleted - filesystem is now ext2 only *** hurtleberry_root: Superblock doesn't have has_journal flag, but has ext3 journal inode. CLEARED. hurtleberry_root was not cleanly unmounted, check forced. hurtleberry_root: Journal inode is not in use, but contains data. CLEARED. hurtleberry_root: Inode 449739, i_blocks is 448, should be 104. FIXED. hurtleberry_root: Inode 942059 has illegal block(s). hurtleberry_root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) fsck failed. Mounting root device read-only. Mounting root /dev/system_hurtleberry/root ext3: No journal on filesystem on dm-1 mount: wrong fs type, bad option, bad superblock on /dev/mapper/system_hurtleberry-root, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so could not mount root filesystem -- exiting to /bin/sh $ have to check if its a hardware bug or if it also happens on other disks. At least a previous similar 11.0 installation turned the ext3 also into ext2. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=405264 User olh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=405264#c1 --- Comment #1 from Olaf Hering <olh@novell.com> 2008-07-01 04:25:19 MDT --- appears to work on another system: doing fast boot Creating device nodes with udev udevd-event[290]: node_symlink: device node '/dev/mapper/control' already exists, link to '/dev/device-mapper' will not overwrite it blogd: can not open pty/tty pair: No such file or directory mdadm: device 1 in /dev/md0 has wrong state in superblock, but /dev/sda2 seems ok mdadm: /dev/md0 has been started with 2 drives. 3 logical volume(s) in volume group "system_cherry" now active 3 logical volume(s) in volume group "system_cherry" now active Waiting for device /dev/system_cherry/root to appear: ok fsck 1.40.8 (13-Mar-2008) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/system_cherry/root cherry_root: clean, 116089/2232048 files, 856508/8922112 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/system_cherry/root INIT: version 2.86 booting -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=405264 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |mkoenig@novell.com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=405264 Olaf Hering <olh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Found By|--- |Development -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=405264 User coyli@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=405264#c2 coly li <coyli@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coyli@novell.com Status|NEW |NEEDINFO Info Provider| |olh@novell.com --- Comment #2 from coly li <coyli@novell.com> 2008-12-02 07:29:43 MST --- Just want to confirm if the boot partition is also placed in lvm. And can this issue be reproduced on opensuse 11.1 ? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=405264 User olh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=405264#c3 --- Comment #3 from Olaf Hering <olh@novell.com> 2008-12-08 09:28:45 MST --- I have to retest this setup. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=405264 User olh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=405264#c4 Olaf Hering <olh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|olh@novell.com | --- Comment #4 from Olaf Hering <olh@novell.com> 2009-01-15 04:21:22 MST --- with sles11rc2: running 51-md.sh mdadm: device 1 in /dev/md/0 has wrong state in superblock, but /dev/sdb2 seems ok mdadm: /dev/md/0 has been started with 2 drives. preping 61-lvm2.sh running 61-lvm2.sh 3 logical volume(s) in volume group "system_huckleberry" now active 3 logical volume(s) in volume group "system_huckleberry" now active preping 81-resume.userspace.sh running 81-resume.userspace.sh preping 82-resume.kernel.sh running 82-resume.kernel.sh preping 83-mount.sh running 83-mount.sh Waiting for device /dev/system_huckleberry/huckleberry_root to appear: ok node name not found fsck 1.41.1 (01-Sep-2008) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/system_huckleberry/huckleberry_root huckleberry_root: clean, 112256/1245184 files, 804830/4980736 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/system_huckleberry/huckleberry_root so, why does it have wrong state in superblock? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=405264 Hendrik Vogelsang <hvogel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=405264 Hendrik Vogelsang <hvogel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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.
participants (1)
-
bugzilla_noreply＠novell.com