I can accept this. It didn't cross my mind to try to inject the option there. Thanks.
-----Original Message----- From: Michael Tautschnig [mailto:m...@debian.org] Sent: Sunday, February 21, 2010 3:48 PM To: Joseph M. Deming; 570...@bugs.debian.org Subject: Re: Bug#570117: fai-client: fai-setup using software raid1 as boot/root First of all, sorry for taking so long to respond. > Package: fai-client > Version: 3.3.2 > > First, I want to clarify that this bug is NOT directly fault of fai, > it is again due to other key packages and changes in fundamental > behavior that drive me NUTS when it is changed with so little > consideration, but it seems you may still wish to change things on > your end to stay up with the curve. > > mdadm 3.1.1(-1?) changes the DEFAULT metadata flag from the prior > 0.90, to 1.x; which effectively translates to 1.1 as the > default/stable 1.x metadata format. This chokes up ALL attempts to > use these raid devices as either boot or root in my testing at least. > All of this behavior manifests itself when building a standard sid > system using fai and the current tree, and I fear it will propagate > down sooner or later, at least to squeeze if it's not already there too. > > Further evidence of this issue and 'reasons' as to why it's not fixed > can be found in these bug reports: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569107 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492897 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554500 > > Long story short, since you control the mdadm calls in your fai build > scripts, if you add the option -e 0.90 (or long tag --metadata=0.90) > To the create/partition script when creating the mdadm raid arrays, > specifically for boot/root partitions, I think we all win and you beat > this for the long-term until mdadm/bootloader people get their crap > straight and take the full user base into consideration. Right now, > netinst is broken using raid1 and I'm having to manually destroy and > re-create the partitions to boot any new software raid system setups.... > grrrr. If you care about my stress levels please be sure to modify > setup-storage as well as the old standard as I use setup-storage. Not > sure if the old method even supports software raid, I forget =) > I'm not that fond of the idea of enforcing something outdated, it will likely come back on us at some point. The problem is that once we enforce this, no one can easily override it. Assuming that the maintainers of all the involved packages will do their job sooner or later, I think this is not an issue forever. Of course, however, we need a workaround. And that is already there: If you just add mdcreateopts="-e 0.90" to each of those raid volume definitions you should be fine. Now I understand that this is some extra per-volume work for you, but it is a workaround only, so shouldn't be there forever :-) A full example would look like this: disk_config raid raid1 / hda1,sda1 ext3 rw mdcreateopts="-e 0.90" raid1 swap hda2,sda2 swap sw mdcreateopts="-e 0.90" Is that acceptable to you? Could you verify that it actually does the trick? > Thanks, you guys maintain a great piece of software doing an amazing > thing that linux enjoys making very difficult! > You're welcome :-) And thanks for the very detailed bugreport! Best, Michael PS.: I suggest we leave this bug open for another year or so, until all the mentioned bugs are fixed. We could actually do nice blocking tags, if someone so desires... __________ Information from ESET NOD32 Antivirus, version of virus signature database 4887 (20100222) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
