![[LWN Logo]](/images/lcorner.png) |
|
![[LWN.net]](/images/Included.png) |
From: Neil Brown <neilb@cse.unsw.edu.au>
To: linux-raid@vger.kernel.org
Subject: ANNOUNCE: mdctl 0.4 available for testing
Date: Thu, 26 Jul 2001 19:26:20 +1000 (EST)
Hi,
I finally got back to working on mdctl after a month's hiatus and
have just put version 0.4 up at
http://www.cse.unsw.edu.au/~neilb/source/mdctl/
This version includes proper parsing of the config file as well as a
number of small fixes.
The config file (/etc/mdctl.conf by default) contains devices lines:
DEVICE /dev/hd[abc]1 /dev/sda[123]
which list devices that should be scanned for RAID super blocks, and
array lines:
ARRAY /dev/md0 UUID=79c68855:bab611b5:dcbebd2e:bd2b8d29
which list md devices and the UUID of the array to assemble there.
Given this, a command like:
mdctl --Assemble --scan --verbose --configfile=/etc/mdctl.conf
or just
mdctl -Asv
will scan those devices, find all the parts to make up each array,
and will assemble them.
Also, I have changed the way that RAID5 arrays are created so that
they are always created with one drive missing, and with a spare.
This means that a "reconstruct" process is used to make parity right,
instead of a resync process. Recontruction is much faster than
resync when most of the parity if wrong.
I plan to use mdctl exclusivly now - not more mkraid/raidstart/etc,
so hopefully I will find and iron out any usability/correctness
issues. If anyone else would like to try using it, I would
appreciate any feed back.
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org