Its my understanding that the filer will not (by default) allow you to consume
all disks in a system and leave no spares. (this answers the initial issue of
running out of spares)
But on the other hand pre-installation planning cannot be over stated.
-----Original Message-----
From: Tuc [mailto:ttsg@ttsg.com]
Sent: Monday, August 28, 2000 6:51 PM
To: mikey(a)remedy.com
Cc: toasters(a)mathworks.com
Subject: Re: Removing disks from a volume
>
> I agree, I think this is a really good idea for an enhancement request.
> Especially useful for inexperienced admins (or those muddle-headed from
> their 4th 18-hour day this week).
>
After this weekend, an option that double checks when you initially
install the filer to ask "I know you said you wanted to add 2 disks to the
root group, did you really mean this or was it 2 disks total you want in
the root group". Only took me an hour to recover, but STILL!
Thanks, Tuc/TTSG
> -----Original Message-----
> From: Jeffrey Krueger [mailto:jkrueger@qualcomm.com]
> Sent: Monday, August 28, 2000 10:37 AM
> To: Brian Tao
> Cc: Mike Sphar; toasters(a)mathworks.com
> Subject: Re: Removing disks from a volume
>
> On Sat, Aug 26, 2000 at 11:12:14AM -0400, Brian Tao wrote:
> >
> > Indeed... recovery could be costly and/or awkward. Perhaps Netapp
> > would consider a "safety feature" enhancement for "vol add/create"
> > command where by default it will not allow a situation in which a
> > volume/raidgroup is left with no hot spares. Add a "-f" switch (or
> > whatever) to force an override. Warm fuzzy feature. :)
>
> This is a great idea. And should be only a couple line of intern-level
> code to implement too.
>
> -- Jeff
>