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

Question

Question

volume locked or currently in use [9022]

asked on March 25, 2014

Good Morning!

 

I'm currently attempting to Limit the size on a Physical Volume so that Rollover can occur before the Volume fills.

 

The Volume size is currently around 2TB and I want to set it to Rollover at around 1.6TB so there is some room for movement. I've done this before but in this instance i'm getting a message that the volume is locked or currently in use. The volume doesnt appear to be locked and i've attempted to do this task on a weekend to ensure its not in use.....to no avail. Please see below screenshot.

 

 

Lf_Volume_locked.png
0 0

Replies

replied on March 25, 2014

Have you tried disabling the volume before adjusting the rollover size? Its in the general tab of the volume properties.

0 0
replied on March 25, 2014

I'm trying to do this without downtime if possible.....

0 0
replied on March 25, 2014

Was this a Physical Volume or a Logical Volume when you created it? Once created you cannot switch from one to the other. I also don't see how you can set the size smaller than what it currently is. Seems to me you should create another Logical Volume with the proper size limits and migrate the files from the existing to the new. Just my two cents.....

0 0
replied on March 25, 2014

Hi John,

 

Thanks for your post, you certainly can downsize a volume and technically you can create volume limits which are larger than any physical capacity actually given to the system (which can lead to problems!). In this case the volume only has 500GB or so in use so setting a 1.6TB limit is perfectly fine..

 

Its a Physical volume belonging to a Logical Volume.

0 0
replied on March 25, 2014

I know that we had this issue with LF 8.1 and we resolved it by disabling the volume, then restarting the LF Server service. We have not had an issue changing volume sizes in the newer versions of LF.

Have you checked if there is another process running that is causing the error (I have seen this error when re-indexing)?

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

Sign in to reply to this post.