On 10/11/99 07:41:30 you wrote:
The volume could be offline, that's for sure, but why the machine ?
This is the result of a less-than-thorough multivolume implementation plan. Originally, there only *was* one volume, so taking the whole filer down wasn't an issue. Presumably when mutlivolume was to be implemented, Netapp decided it was more important to get that out the door than to spend more time and resources modifying a better wack interface to run on an offline volume while the system remained up.
Note that this is also different from a request for a completely online wack on an active filesystem, or allowing a filesytem to remain online read-only while being wacked. I still question the utility of the latter, but it might be good as part of an automated process strategy (just as snapshots are created for dump). Anyway, these are all very different enhancements. Netapp will have to decide which ones to implement, and which ones to implement first.
Bruce