https://bugzilla.novell.com/show_bug.cgi?id=879384 https://bugzilla.novell.com/show_bug.cgi?id=879384#c1 --- Comment #1 from Dennis Olsson 2014-05-22 12:36:18 CEST --- Sorry, was a bit too fast in claiming that the above supplied patch would serve as a usable word-around patch. The patch allows for the "mkinitrd" script to actually finish its work, but unfortunately the "etc/mdadmin.conf" file in the generated "initrd" file is not correct -- In my case the definition for the "/dev/md/data" MD RAID device is missing, and without this definition the MD RAID device for the root file system does not get started cleanly. Consequently, please, do *not* use the above supplied patch. Not only does it not work, it results in a non working system after rebooting. -- 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=879384 https://bugzilla.novell.com/show_bug.cgi?id=879384#c2 --- Comment #2 from Dennis Olsson 2014-05-26 13:23:19 CEST --- Created an attachment (id=592006) --> (http://bugzilla.novell.com/attachment.cgi?id=592006) Patch of "/lib/mkinitrd/scripts/setup-md.sh" (against "mdadm-3.3-4.4.1"). Attached patch of "/lib/mkinitrd/scripts/setup-md.sh" solves the reported problem correctly. The patch enables the resolving of multi level used MD RAID devices into their physical block devices independently of the level of MD RAID device definitions used. -- 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=879384 https://bugzilla.novell.com/show_bug.cgi?id=879384#c4 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |DOlsson@WEB.de --- Comment #4 from Neil Brown 2014-06-10 05:45:10 UTC --- Hi thanks for the fix. Unfortunately you had made lot of unnecessary changes which made it hard for me to remove. So I've removed most of those to get something where I can easily see just what has been changed. I appreciate that I saw them as improvements and generally improving code is good. However openSUSE is moving to dracut instead of the old mkinitrd, so this is dead-end code and stability is more more important that tidy-ups. I removed the changes to check /dev/md/* as well as /dev/md* as they are always symlinks and I think it is easier to use "readlink --canonicalize" to resolve them. Can you test the result, which I will attach, to ensure I didn't break anything? 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=879384 https://bugzilla.novell.com/show_bug.cgi?id=879384#c6 Dennis Olsson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|DOlsson@WEB.de | --- Comment #6 from Dennis Olsson 2014-06-11 11:24:00 CEST --- Hi Neil, Thanks for your review and comments. Using the "readlink --canonicalize" is a real neat way of solving the symlink problem, I had a hand in this script -- thanks for the hint. Although I can sympathies with your "complaint" about not being able to see what has been fixed, I still do not get the idea of not doing code tidy-ups at the same time, when one is doing bug fixes. Sure, you cannot know (because I did not tell you ;-) that the fix supplied already had gone through various iterations before ending up with the fix attached to this report. But, I suppose that has something to do with working style, and how one was taught how to do "real programming, right (including very thoroughly testing of ones code)". :-) Personally, I would prefer that shell scripts that claims to be Bash Scripts (by the usage of "#!/bin/bash") also use the Bash Syntax and Features, instead of using the old antiqued Shell syntax -- But, as I wrote earlier, this seems to be more of a personal working style. Yes, I have read above openSUSE moving to "dracut", although I have not been able to figure out, when this is going to happen (can "dracut" be used instead of "mkinitrd" on openSUSE 13.1??), and since this bug is real today and prevents the correct set up and usage of the system, it still needs to be fixed. Anyway, your version of the fix is an almost one-to-one match with one of my very early tries, and it does to its job correctly, too. :-) The only minor typo that should be fixed is in the last comment line, where "..., created needed udev ..." should read "..., create needed udev ...". The typo was in my fix -- sorry about that. ;-) -- 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=879384 https://bugzilla.novell.com/show_bug.cgi?id=879384#c8 --- Comment #8 from Bernhard Wiedemann 2014-06-12 02:00:12 CEST --- This is an autogenerated message for OBS integration: This bug (879384) was mentioned in https://build.opensuse.org/request/show/236928 13.1 / mdadm -- 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=879384 https://bugzilla.novell.com/show_bug.cgi?id=879384#c10 --- Comment #10 from Swamp Workflow Management 2014-06-20 10:04:22 UTC --- openSUSE-RU-2014:0820-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 879384 CVE References: Sources used: openSUSE 13.1 (src): mdadm-3.3-4.8.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.