On Tue, 10 Nov 1998, Hardware Stuff wrote:
> I noticed that top shows an mdrecoveryd process, it's existance
> puzzles me. Based on skimming the list about recent RAID5 changes, I
> had thought that such a process would only exist for reconstruction of
> a RAID5 disk set. While I did initially enable all RAID options, my
> recent kernel builds have been exclusively RAID0. /proc/mdstat
> confirms only a RAID0 personality.
>
> What does mdrecoveryd do for a RAID0 system? Perhaps the name is
> misleading?
you could load a RAID1/5 module later on ... but you are right, it could
be started dynamically too.
Thanks for the information.
While on the subject of RAID0, I also wondered about a single
superblock for the autostart information. Since I've experienced
superblock corruption on a Solaris system, and recovered from it by
utilizing one of the superblock copies, could this be a single point
failure location? Can the RAID code stash a superblock copy
elsewhere, or is it easily recreated from the /etc/raid0.conf file?
Thanks again for the incredible RAID code, with the autostart in
place, my Solaris friends cannot be snobs anymore ;-)
