This of course suggests that the raidtab file is almost redundant itself and
could be replaced by command-line options to mkraid. mke2fs certainly
doesn't require an fstab entry for a filesystem before it can be created or
dealt with. raidtab should be a place to keep information in case the
persistant superblock is somehow damaged, imho.
For example:
mkraid --level=5 --device=/dev/md0 --add=/dev/sda5 --add=/dev/sdb5
--add=/dev/sdc5 --addspare=/dev/sdd5
Creating /dev/md0 with:
/dev/sda5 - disk 0
/dev/sdb5 - disk 1
/dev/sdc5 - disk 2
/dev/sdd5 - spare 0
.........................Finished.
Michael Robinton wrote:
> I'm in the process of upgrading another production system from old tools
> to new and noticed that you can't do a "raidstop" unless there is a valid
> raidtab. It seems to me that with a persistent superblock, this should
> not be necessary. The same applies to raidstart. Unless there is some
> reason to change the raid configuration -- i.e. remove or deactivate a
> piece, the superblock should provide all the necessary information. For
> raid to go mainstream, these minor things should be cleaned up. The docs
> seem to indicate that once the mkraid is done, the raidtab is really not
> needed. That is not true in the case with raidstop, raidstart, initrd
> starts and raid over raid (10, 51, etc...). All the info is there, the
> raidtab is redundant and will cause errors if not up todate or is missing.
--
_____/~-=##=-~\_____
-=+0+=-< Michael T. Babcock >-=+0+=-
~~~~~\_-=##=-_/~~~~~
http://www.linuxsupportline.com/~pgp/ ICQ: 4835018
