> The functionality of ckraid is automatically performed by kernel on startup
> of raid devices.
Is there a way to say "check the current status in verbose mode" ?
/proc/mdstat shows the "bare bone" info, but not things like spare disks, etc.
> raidhotadd /dev/md0 /dev/sda2
Ta -- it's not actually mentioned anywhere except for the src [ :-) ] and the
Makefile. As I didn't do a "make install", I didn't notice it :-(
Any instructions on how to use it ?
> Raidhotadd just adds the devices as spare disks,
Does one have to manually update /etc/raidtab to show which disks are now
"spare" and which are the main disks ?
>> If I wasnt to test things, I can raisdtop, ZAP a partition, but cannot then
>> attempt a restart -- the only way I can do it is to reboot. Is there a way
>> to tell a running system to take a close look at a MD partition ?
> Huh? you can allways mannualy start/stop the device using raidstart/raidstop
It fails when I try it :-(
>> Is there a way to add superblock info to an existing partition without
>> ZAPping it ? e.g. take a std partition, resize2fs it down a bit, add a SB,
>> then set up a second miiror disk, and get the system to copy it over, etc ..
> No. There is however another way to do this: use the "root raid install
> patches" (posted last week, see archive at
Ta -- but I already *HAVE* the data -- I want to make it RAID1 ...
Also, how do I add a persistent super block to an old linear or RAID0 FS ?
% md7: WARNING: hda11 appears to be on the same physical disk as hda10. True
% protection against single-disk failure might be compromised.
Quite true for raid[145], but irrelevant for linear ...
If I take a clean Linux 2.2.3, apply raid0145-19990309-2.2.3, type
"make bzImage" (zImage is too large), install it and reboot, I get
Out of memory\n\n\n -- System halted
i.e. arch/i386/boot/compressed/misc.c:malloc -- any ideas how to avoid this ?
Does anyone have utilities to peek/poke SBs ?
If not, should I write private perl scripts to do the HACKs I want, or should
I write some C code to contribute to the package -- or would it be too
dangerous to let loose ? Things like:
1) Display the location of an SBs on a partition (or all partitions)
2) check SBs are consistent
3) display the contents of an SB
4) ZAP an SB
5) read an SN to file
6) write an SB from file
7) write an SB from other SBs
8) convert an SB to the format expected by /etc/raidtab
9) move the SB after/before a grow/shrink of the partition
I realise that "the kernel does that automatically" for at least some of the
above, but I want to be able to do things manually ...
