>> [root@xxxxxx raidtools-0.90]# mkraid --force /dev/md0
>> DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
>> handling MD device /dev/md0
>> analyzing super-block
>> disk 0: /dev/sdb1, 4188937kB, raid superblock at 4188864kB
>> disk 1: /dev/sdc1, 4188937kB, raid superblock at 4188864kB
>> mkraid: aborted
Yes, it's not too helpful about saying *WHY* it fails :-(
> - fdisk your disks to remove the partitions that will be in the raid.
> Completely remove them, don't just change the partition type.
> - reboot.
> - fdisk your partitions into existence, with type 'fd' as advertised in
> the doc. Do not reboot.
Err -- is anything mounted on the disk ?
If so, it will fail to re-read the partition table, so you will not be able
to access the partition at all !
If all you want is to stop the kernel from reading and using the old SB,
isn't it sufficient to *EITHER* change the partion type *OR* ZAP the SB ?
Sure -- may as well play safe and do both :-))
In any case, even if ther is a "keep fd open" bug, ZAPping both SB and
partition type (belt and braces) should mean that a reboot will get it clear.
> While I'm here, I see a lot of questions in this list about how to get
> RAID working, but none from people reporting bugs in the software once it
> is up and running, or serious loss of data from nasty incidents etc. I
> want to install Linux-RAID in a production environment, but I cannot find
> any solid information about other peoples experiences in such an
> environment.
I suspect that people may be too embarassed wgen they scr*w up :-)
> If anyone out there has any long-term experience with Linux-RAID in a
> production environment would they please let me know (either directly or
> via this list). Obviously, with the tools being updated constantly,
> 'long-term' might mean only a couple of weeks
Well, I've been using raidtools-0.50 for months (linear and raid0) for
spare local disk. Users know it's just "scratch" space, but so far, I've
not had a problem !
I've recently moved to raidtools-0.90 (linear, raid0 and raid1), and it
*seems* to be OK, but I feel it should be so much easier than it is to upgrade
filing systems, manipulate SBs, etc.
Also, as I mentioned, 2.2.3 + raid145 patches fails at uncompress time saying
"Out of memory" :-(( So stuck with 2.2.2 ...
