From what I can see from the audit logs they ran "ndmpcopy
/vol/old_vol0 /vol/vol0" after they had renamed the original vol0 to old_vol0.
I checked the audit logs on the test system and they did the ndmpcopy from vol0 to new_vol0, then did the rename. Would running the ndmpcopy when the original vol0 had been renamed first affect any of the files or the copy somehow? I wouldn't expect so, but I'll have him try it again in the morning.
Jeff
On Dec 14, 2011, at 2:10 PM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:
Greetings,
We have a filer (3140) running 8.0.1 and the group wanted to convert it to a 64 bit root aggregate and vol0. I let them practice on my 8.1 test box and everything went as planned. When they did it on their 8.0.1 box, all went as plan except for the assigning the root volume.
They had moved the original vol0 out of the way and renamed the new 64 bit volume to vol0. When they ran the "vol options vol0 root" command it gave the following output:
Necessary system files are not present on the volume 'vol0'. It is recommended that you copy system files from the current root volume to the new root volume using the steps outlined in System Administration Guide, chapter 'Understanding Root Volumes', section 'Changing Root Volume'. If you do not, then after reboot, the appliance will enter setup and service will be disrupted until all the setup steps (including a reinstall of system software) have been completed. Continue with set root operation (y/n)?
He answered no. We did file listings and verified all the files are in both places. There were no obvious ndmpcopy errors. The size of space used differs a little bit, but I assume the 32 vs 64 bit aggregate layouts would cause some fluff. I even had him destroy the 64 bit vol0 volume and run everything again. Same results.
Does anyone know what this is complaining about?
Thanks,
Jeff