On 04/22/2010 02:34 AM, Res wrote:
> On Wed, 21 Apr 2010, Karl Larsen wrote:
>>> 4. Your raid5 problems are typical.
>> Then this is an installer problem, over the years I have done many raid
> system OS upgrades (but only on slackware) with not a single issue, no
> reason why ubuntu (or fedora since someone mentioned its a problem there
> as well) cant have the same reliability in this procedure either, so it
> comes down to the application responsible for that task.
>> If ubuntu (or fedora) are incapable of doing something this simple,
> perhaps those worried should use an alterntive OS on the machine that
> holds that very important data. This is 2010 FFS, not 1991.
I've been following this thread and I think I'm the only person who made
a reference to Fedora. What I experienced in Fedora was NOT a problem. I
think it was prudent behaviour. In short, I could not do a kickstart
installation and tell the installer to remove all partitions if a drive
had previously been part of a RAID set. I tried to find a reference to
this in the Fedora mailing lists but ended up finding something else
that was similar to the original poster's problem. See:
<<https://bugzilla.redhat.com/show_bug.cgi?id=543749> in the Red Hat bug
tracker. That looks like a udev problem and someone posted a workaround.
If Slackware also uses udev and this is a udev problem, Slackware would
also be similarly affected while "doing something this simple".
--
Regards,
Clifford Ilkay
Dinamis
1419-3266 Yonge St.
Toronto, ON
Canada M4N 3P6
<http://dinamis.com>
+1 416-410-3326