[Bug 340971] New: mkinitrd stumbles over UUID mount for root filesystem
https://bugzilla.novell.com/show_bug.cgi?id=340971 Summary: mkinitrd stumbles over UUID mount for root filesystem Product: openSUSE 10.2 Version: Final Platform: x86 OS/Version: openSUSE 10.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: pieter.hollants@novell.com QAContact: qa@suse.de Found By: --- mkinitrd stumbles over an fstab entry like this UUID=8d9a6447-24a0-41e8-ad8b-04229b233f92 / ext3 acl,user_xattr 1 1 with the error message error on stat() /dev/disk/by-uuid/8d9a6447-24a0-41e8-ad8b-04229b233f92: Datei oder Verzeichnis nicht gefunden ie. file not found. It will continue to run, but not include necessary modules into the initrd (such as ide-core, ide-disk etc. in this particular case). If the fstab entry is changed to read /dev/md0, mkinitrd runs correctly, including even more modules than needed to boot correctly. -- 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=340971#c1 --- Comment #1 from Pieter Hollants <pieter.hollants@novell.com> 2007-11-12 04:32:34 MST --- Argh. Wrong UUID. So, strictly speaking, INVALID. However, could it be possible to add a more verbose error message to mkinitrd, causing it to abort what it can't stat()? -- 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=340971#c2 --- Comment #2 from Pieter Hollants <pieter.hollants@novell.com> 2007-11-12 04:37:00 MST --- I hate to followup myself, but, what still makes a bit nervous is this: Root device: UUID=cb9e1c18-d895-4be2-8303-c4d1fe6e85f1 (/dev/sdb1) (mounted on / as ext3) The filesystem UUID is physically present on /dev/md0, thus /dev/sda1 AND /dev/sdb1, but it reports just the latter. Is it safe to assume that, whatever mkinitrd stats the device for, works correctly even if only a single disk of the RAID array is touched? -- 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=340971 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com AssignedTo|kernel-maintainers@forge.provo.novell.com |hare@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=340971#c3 Lars Marowsky-Bree <lmb@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lmb@novell.com --- Comment #3 from Lars Marowsky-Bree <lmb@novell.com> 2007-11-14 04:18:28 MST --- No. RAID must _always_ be accessed through the RAID layer (/dev/md*). This will not work correctly. -- 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=340971#c4 Hannes Reinecke <hare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #4 from Hannes Reinecke <hare@novell.com> 2007-11-16 03:13:08 MST --- And I must say the error indicates it quite clearly. It tries to mount a device / file which isn't there. _Why_ it isn't there is exactly the task of the admin to find out. mkinitrd cannot really know that you did a spelling error :-) And for the RAID device: The mkinitrd should be created with RAID support, otherwise it won't be able to start the RAID and hence it'll try to access the underlying devices. Doesn't do much harm in your case (as you're most likely running a mirrored RAID), but in general it won't work. If we were misdetecting the RAID then this would be a bug; but a different one, please. -- 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=340971#c5 --- Comment #5 from Pieter Hollants <pieter.hollants@novell.com> 2007-11-16 03:23:08 MST --- To repeat: apparantly mkinitrd tries to stat() the root device. Why I don't know yet. However, it is obviously necessary since the generated initrd differs fatally between failure and success of the stat(). The bug is there in that mkinitrd continues in spite of the failed sync. My point was not that mkinitrd should start fireworks, call 911 or similar but the current behaviour of silently continuing results in a unusable initrd. Please either correct my impression that the stat() is necessary (and shortly explain why it is done then) or make mkinitrd really abort when it can't stat(). -- 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=340971#c6 --- Comment #6 from Pieter Hollants <pieter.hollants@novell.com> 2007-11-16 03:25:17 MST --- Also, with regard to Lars' comment, it's not about RAID support in the created initrd, but the output of the mkinitrd run itself: Root device: UUID=cb9e1c18-d895-4be2-8303-c4d1fe6e85f1 (/dev/sdb1) (mounted on / as ext3) Apparantly mkinitrd tries to find the device belonging to the UUID and ends up using one of the two disks of the RAID, instead of the RAID device itself. My question - resulting from the question what the stat() in mkinitrd does - was whether this could do any harm, Lars suggested it does. -- 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=340971#c7 Hannes Reinecke <hare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #7 from Hannes Reinecke <hare@novell.com> 2007-11-16 03:37:36 MST --- Where is the root device actually mounted? Is it /dev/md0? Please attach the output of cat /proc/mounts and bash -x /sbin/mkinitrd. Thanks. -- 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=340971 Hannes Reinecke <hare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |pieter.hollants@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=340971#c8 --- Comment #8 from Pieter Hollants <pieter.hollants@novell.com> 2007-11-17 04:31:28 MST --- Created an attachment (id=183784) --> (https://bugzilla.novell.com/attachment.cgi?id=183784) /proc/mounts output -- 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=340971#c9 Pieter Hollants <pieter.hollants@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|pieter.hollants@novell.com | --- Comment #9 from Pieter Hollants <pieter.hollants@novell.com> 2007-11-17 04:34:31 MST --- Created an attachment (id=183785) --> (https://bugzilla.novell.com/attachment.cgi?id=183785) Output of bash -x /sbin/mkinitrd -- 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=340971#c10 --- Comment #10 from Pieter Hollants <pieter.hollants@novell.com> 2007-11-17 04:38:14 MST --- I see what you probably wanted to look for: hermes:/home/pief # ls -la /dev/disk/by-uuid/ [...] lrwxrwxrwx 1 root root 10 11. Nov 17:23 cb9e1c18-d895-4be2-8303-c4d1fe6e85f1 -> ../../sdb1 [...] You're suggesting this is not really a bug in mkinitrd, right? -- 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=340971#c11 Hannes Reinecke <hare@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hare@novell.com AssignedTo|hare@novell.com |kasievers@novell.com Status|REOPENED |NEW --- Comment #11 from Hannes Reinecke <hare@novell.com> 2007-11-21 04:33:21 MST --- No, this is actually udev doing things wrong. By rights the symlink should be pointing to /dev/md0, not sdb1. Kay, I think we need to do the overwrite magic here, too. -- 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=340971#c12 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |pieter.hollants@novell.com --- Comment #12 from Kay Sievers <kasievers@novell.com> 2007-11-21 07:38:54 MST --- Which udev version is that: "rpm -q udev"? I guess it is fixed in version 105: http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=ac77e95948edc... -- 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=340971#c13 Pieter Hollants <pieter.hollants@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|pieter.hollants@novell.com | --- Comment #13 from Pieter Hollants <pieter.hollants@novell.com> 2007-11-21 12:00:02 MST --- pief@hermes:~> rpm -q udev udev-103-12 -- 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=340971#c14 --- Comment #14 from Kay Sievers <kasievers@novell.com> 2007-11-21 12:06:02 MST --- I expect it is fixed with openSUSE 10.3. Any plans to update soon, so we could verify this? -- 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=340971#c15 --- Comment #15 from Pieter Hollants <pieter.hollants@novell.com> 2007-11-22 11:13:13 MST --- Not really. I can try to reproduce within VMware with 10.3, but only if this could trigger a udev update for 10.2, otherwise I'm stuck anyway ;) -- 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=340971 User kasievers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=340971#c16 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #16 from Kay Sievers <kasievers@novell.com> 2008-01-10 09:33:01 MST --- I expect this is fixed in openSUSE10.3. -- 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