Date: Thu, 2 Oct 2003 20:05:22 -0600 (MDT) From: Scott Long <scottl@freebsd.org> To: Josh Brooks <user@mail.econolodgetulsa.com> Cc: freebsd-scsi@freebsd.org Subject: Re: confusing aaccli output ... Message-ID: <20031002195954.X36855@pooker.samsco.home> In-Reply-To: <20031002111227.E54619-100000@mail.econolodgetulsa.com> References: <20031002111227.E54619-100000@mail.econolodgetulsa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031002195954.X36855>