On Wed, Feb 10, 1999 at 09:43:12AM -0600, Chris Price wrote:
> We should not criticize Redhat for putting obsolete code on their
> distro. A while back, when Redhat followed a more bleeding edge approach,
> they constantly put beta software on their distro, and received much more
> criticism for it - hence the resulting obsolete inclusions.
>
i'll answer since i was one of the first to point fingers at redhat
for their raid implementation, and i did not do that because they put
an old (but working, it is in beta, while all later patches are in
alpha state) implementation of raid. But for the careless way they
integrated raid into the distributions
let's see /etc/rc.d/rc.sysinit
they do
activate swap
check/mount/quotaon root
activate modules/pnp/stuff
load sound modules (?)
>>>> raidrun -a
>>>> (if it fails shell, then reboot)
check non root fs
>>>> (if it fails shell, then reboot)
clear locks/tmp junk
set clock/serials/modules
unconditionally load the st module (doing some weird and useles greps ???)
beside some unclean shell programming, they do not raidstop before
reboot. So you have two cases in which you'll have to resync
if you don't do raidstop after fixing in the shell prompt.
1) you have more than 1 md device and not all of them fail
2) fsck fails
then take a look at /etc/rc.d/init.d/halt:
kill process
umount fs
>>>> stop raid
mount readonly all fs you could not umount
halt
just pray you did not have a hung process that kept you
from unmounting that 100Gb raid partition
> Instead of pointing fingers at Redhat, I would ask if there is
> someone with teh Linux-raid community that actively corresponds with
> redhat to let them know of current status of linux-raid? Ingo etal. seem
there was someone from redhat on this mailing list just begore
they released 5.2 but they have disappeared since.
> to be doing a superb job in adding funtionality and fixing bugs quickly,
> but that does result in a myriad of patches being issued fairly
> regularily -> is it Redhat's responsibility to keep track of linux-raid,
> or is it our responsibility to inform them of stable releases?
I tought it was their responsability. Anyway I won't post any bugfix
to a mailbot that answers suggesting you did something wrong
and directs you somehwere else for help.
Regards,
Luca
--
Luca Berra -- [EMAIL PROTECTED]
System and Network Manager - CoMedia s.r.l.
