Some first-try comments on RAID groups: the order in which disks get added to new RAID groups is pretty screwy. Group 0 was the original v4.1 group and I just created group 1. Group 0 is pretty straightforward. Group 1 is not.
It would be nice if one of the following was implemented:
- there was also some sort of "fake" command that would show you what would be done if you tried a certain command. Since this was my first experience with setting the volume raidsize, I wasn't 100% certain where the next disk I added. - a way to abort disk additions while they are still being added
Basically, since disk changes are non-reversible, there should be some comfort/safety margin for configuring things the way you want them to be configured.
Other than that, it wasn't too bad, although I'm starting to find the "vol" command really awkward to use.
Dan
------- start of cut text -------------- thorium> sysconfig -r Volume vol0
RAID group 0
RAID Disk HA.Disk_ID Used (MB/blks) Phys (MB/blks) --------- ---------- -------------- -------------- parity 8a.1 8600/17612800 8683/17783112 data 8a.2 8600/17612800 8683/17783112 data 8a.3 8600/17612800 8683/17783112 data 8a.4 8600/17612800 8683/17783112 data 8a.5 8600/17612800 8683/17783112 data 8a.8 8600/17612800 8683/17783112 data 8a.9 8600/17612800 8683/17783112 data 8a.10 8600/17612800 8683/17783112 data 8a.11 8600/17612800 8683/17783112 data 8a.12 8600/17612800 8683/17783112 data 8a.13 8600/17612800 8683/17783112 data 8a.14 8600/17612800 8683/17783112
RAID group 1
RAID Disk HA.Disk_ID Used (MB/blks) Phys (MB/blks) --------- ---------- -------------- -------------- parity 8b.14 8600/17612800 8683/17783112 data 8b.13 8600/17612800 8683/17783112 data 8b.12 8600/17612800 8683/17783112 data 8b.4 8600/17612800 8683/17783112 data 8b.8 8600/17612800 8683/17783112 data 8b.3 8600/17612800 8683/17783112 data 8b.5 8600/17612800 8683/17783112 data 8b.9 8600/17612800 8683/17783112 data 8b.1 8600/17612800 8683/17783112 data 8b.11 8600/17612800 8683/17783112 data 8b.10 8600/17612800 8683/17783112 data 8b.2 8600/17612800 8683/17783112 ------- end ----------------------------
If you want a "neat" looking raid group, you can use the vol command: vol add volname ndisks -d diskname volname=volume name ndisks=num of disks to add diskname= a space separated list of drives that you want to use
vol add vol0 10 -d 8b.0 8b.1 8b.2 8b.3 8b.4 8b.5 8b.8 8b.9 8b.10 8b.11
By the way, want is not straightfoward about Group 1? You have a parity disk, you have data drives, but they are not in order. What is going to happen if/when a disk fails? the spare, wherever it is will get the new ID. Bottom line, with the RAID implimentation, it really does not matter where the disks are, The RAID-manager will take care of it.
Daniel Quinlan wrote:
Some first-try comments on RAID groups: the order in which disks get added to new RAID groups is pretty screwy. Group 0 was the original v4.1 group and I just created group 1. Group 0 is pretty straightforward. Group 1 is not.
It would be nice if one of the following was implemented:
- there was also some sort of "fake" command that would show you what would be done if you tried a certain command. Since this was my first experience with setting the volume raidsize, I wasn't 100% certain where the next disk I added.
- a way to abort disk additions while they are still being added
Basically, since disk changes are non-reversible, there should be some comfort/safety margin for configuring things the way you want them to be configured.
Other than that, it wasn't too bad, although I'm starting to find the "vol" command really awkward to use.
Dan
------- start of cut text -------------- thorium> sysconfig -r Volume vol0
RAID group 0RAID Disk HA.Disk_ID Used (MB/blks) Phys (MB/blks)
parity 8a.1 8600/17612800 8683/17783112 data 8a.2 8600/17612800 8683/17783112 data 8a.3 8600/17612800 8683/17783112 data 8a.4 8600/17612800 8683/17783112 data 8a.5 8600/17612800 8683/17783112 data 8a.8 8600/17612800 8683/17783112 data 8a.9 8600/17612800 8683/17783112 data 8a.10 8600/17612800 8683/17783112 data 8a.11 8600/17612800 8683/17783112 data 8a.12 8600/17612800 8683/17783112 data 8a.13 8600/17612800 8683/17783112 data 8a.14 8600/17612800 8683/17783112
RAID group 1RAID Disk HA.Disk_ID Used (MB/blks) Phys (MB/blks)
parity 8b.14 8600/17612800 8683/17783112 data 8b.13 8600/17612800 8683/17783112 data 8b.12 8600/17612800 8683/17783112 data 8b.4 8600/17612800 8683/17783112 data 8b.8 8600/17612800 8683/17783112 data 8b.3 8600/17612800 8683/17783112 data 8b.5 8600/17612800 8683/17783112 data 8b.9 8600/17612800 8683/17783112 data 8b.1 8600/17612800 8683/17783112 data 8b.11 8600/17612800 8683/17783112 data 8b.10 8600/17612800 8683/17783112 data 8b.2 8600/17612800 8683/17783112 ------- end ----------------------------
-- Timothy A. McCarthy --> System Engineer, Eastern Region. Network Appliance http://www.netapp.com 301-230-5840 Office \ / Page Me at: 301-230-5852 Fax / 800-654-9619
-
Daniel Quinlan -
Timothy A. McCarthy