7 messages in org.freebsd.freebsd-scsiconfusing aaccli output ...| From | Sent On | Attachments |
|---|---|---|
| Josh Brooks | Oct 2, 2003 11:16 am | |
| Scott Long | Oct 2, 2003 7:06 pm | |
| Josh Brooks | Oct 5, 2003 8:30 pm | |
| Aaron Wohl | Oct 10, 2003 3:36 am | |
| Scott Long | Oct 10, 2003 6:40 am | |
| David Raistrick | Oct 10, 2003 7:25 am | |
| David Raistrick | Oct 10, 2003 7:34 am |
| Subject: | confusing aaccli output ... | |
|---|---|---|
| From: | Scott Long (sco...@freebsd.org) | |
| Date: | Oct 2, 2003 7:06:39 pm | |
| List: | org.freebsd.freebsd-scsi | |
On Thu, 2 Oct 2003, Josh Brooks wrote:
Hello,
I had a mirror lose one of its members - after putting a new drive in to replace it (correct size, etc.) I now see this in aaccli:
AAC0> container list Executing: container list Num Total Oth Chunk Scsi Partition Label Type Size Ctr Size Usage B:ID:L Offset:Size ----- ------ ------ --- ------ ------- ------ ------------- 0 Mirror 34.1GB Open 0:00:0 64.0KB:34.1GB /dev/aacd0 mirror0 0:01:0 64.0KB:34.1GB
1 Mirror 68.3GB Open --- Missing --- /dev/aacd1 mirror1 0:03:0 64.0KB:68.3GB
2 Legacy 68.3GB Valid 0:02:0 0.00 B:68.3GB /dev/aacd2
When in reality I expected the controller to automatically rebuild the mirror onto this disk.
What does the "Legacy" keyword mean ?
'Legacy' means that the controller saw a DOS MBR table on the disk, so it assumes that you have valid data on the disk that you might want to access. Maybe this disk had been used previously?
My plan now is as follows:
disk initialize 0,2,0 container set failover 1 (0,2,0)
My questions are as follows:
1. is that procedure correct ? Should I add a `disk verify` between those two commands ?
This should work fine, though my command of the CLI has rusted with age. If you're ultra paranoid, back up the data first =-)
2. Is that procedure safe, as in, won't disrupt the existing mirrors ? (dell has often told me to never initialize a disk with other disks up and running at the same time - is there any real danger, or are they just afraid I will commit a typo ?)
This is likely to be what you suspect. The CLI is very much a 'no seatbelts' app, andquite easy for a small typo to ruin your day. The aac BIOS should also allow you to do what you are aiming for.
Scott