31 Oct
2003
31 Oct
'03
6:18 p.m.
michel.geldenhuys@danone.com (Michel GELDENHUYS) writes:
I discussed this few weeks ago with a NetApp engineer. Unfortunately, this is a "by-design" behaviour: MIB values are loaded during boot and in a random fashion so there is no way to forecast (or enforce) what MIB index will be for a particular volume.
Do you know whether this is the same order that "df" (without arguments) shows the volumes? I have noticed that this changes unpredictably after a reboot. [That's in 6.3.3: I am fairly sure that once upon a time it used to list them in order of Volume-Id (as in the NFS filehandle), and so was consistent over a reboot.]
Chris Thompson Email: cet1@cam.ac.uk