You are viewing limited content. For full access, please sign in.

Question

Question

Volume currently locked or in use. [9022] - can't mark as Read-only, disable, or change fixed path

asked on August 27, 2015

I am trying to change the fixed path of a volume and it will not change. When I try to either change the path, mark the volume as read-only, or disable the volume so I can move it, I get the message that the "volume currently locked or in use. [9022]". 

Our system goes down for backups over night. I came in this morning to try again and I get the same problem. No users are logged into the system that can access the volume or its contents.

What can I do to move the volume?

0 0

Replies

replied on August 27, 2015

Maybe the indexing service has it locked?

 

One way you can fix this is to set the volume to "disabled" then restart the laserfiche service. After it's disabled you can move it and remove the disabled flag. 

0 0
replied on August 27, 2015

I can't set the volume to disabled. I get the same error message.

0 0
replied on August 27, 2015 Show version history

If no one is using LF, can you restart the LF server service then try again?  If that fails, reboot the machine and try again.

0 0
replied on August 27, 2015

There are many people in Laserfiche, so that's not an option, unfortunately. Just no one that has access to the documents in the volume.

0 0
replied on August 27, 2015

Rebooting will be the easiest way to resolve the issue.

0 0
replied on August 27, 2015

I assume, I need to attempt these activities very shortly after the reboot? The server is rebooted nightly and it hasn't solved the problem.

 

To Laserfiche, can I report this as a bug? There should be a way to work with volumes without rebooting the server in a high-availability environment.

1 0
replied on August 27, 2015 Show version history

This sounds like a bug. Try disabling your Laserfiche Full-Text Search Engine service temporarily and see if that helps. We've made some fixes for Laserfiche 10 that will make this less common.

1 0
replied on August 28, 2015

I ended up doing what others have done... restart the services and move the volume before too much activity starts up again.

I appreciate the response and that you agree it is a bug. When I try again, I'll try disabling the full text service.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.