publicweb is a volume in a vfiler (publicweb-vf-01) and yes it could considered the "root" volume in that context (it has the publicweb/etc dir)
I executed the snap restore in the vfiler0 context Maybe being in the publicweb-vf-01 context would have made a difference?
I'm beginning to see why the vfiler creation wizard forces you to create a separate small root volume for each vfiler.
thanks for the feedback !
On Sep 27, 2012, at 2:41 PM, Clear, John wrote:
It looks like publicweb is also your root volume. Doing a snap restore on the root volume is not a good idea.
Even after removing the file, OnTap still has the file handle open on it.
You probably need to create a new separate root volume (recommended) or move the root volume to another existing volume and then re-run the snap restore.
If publicweb isn’t the root volume, I’m not sure what the issue is.
John
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt Sent: Thursday, September 27, 2012 2:32 PM To: toasters@teaparty.net Lists Subject: Error: snap restore: Volume is in use by other operations
Anyone seen this
na03*> snap restore -t vol -s hourly.1 publicweb
Volume publicweb will be made restricted briefly before coming back online.
Are you sure you want to do this? y
You have selected volume publicweb, snapshot hourly.1
Proceed with revert? y Volume publicweb may not be remounted because of 1 open file: The sm_recover_main process has 1 file open : /vol/publicweb/etc/sm/notify snap restore: Volume is in use by other operations. (public web).
We cancelled & deleted all related snap mirrors on the volume and and moved the /etc/sm/notify file out of the way and still could not execute the snap restore - any idea why?
this is Ontap 8.1
thanks