• State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 6584 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unallocated Space

Corrigun
over 6 years ago

How does Quest deal with unallocated space on a volume? Will it just ignore it?

We have one server with a very large primary partition and nothing on it but the OS. I would like to shrink that and leave the unused space as unallocated. One big reason for doing this is if/when I need to recover it I will not need to recover to an even larger partition than it is now.

Thanks

Parents
  • 0 over 6 years ago
    If you were going to 'shrink' a volume I would personally take/force another base image myself so that I made sure that the core updated/modified the disk parameters so that if/when I went to do a BMR it would see the 'new' size of the partition and not continue to use the previous size. I can't validate off hand whether or not the core does this on its own, however I would personally do this.

    Also, I seem to recall that in recent versions we modified this restriction, the fact of having to go to the same size or larger. I can't say that I have officially seen this in documentation, however I do seem to recall it working. Tell ya what, let me spin up a handful of machines and see if indeed my memory is correct or not and try your situation and I'll get back with the results.
Reply
  • 0 over 6 years ago
    If you were going to 'shrink' a volume I would personally take/force another base image myself so that I made sure that the core updated/modified the disk parameters so that if/when I went to do a BMR it would see the 'new' size of the partition and not continue to use the previous size. I can't validate off hand whether or not the core does this on its own, however I would personally do this.

    Also, I seem to recall that in recent versions we modified this restriction, the fact of having to go to the same size or larger. I can't say that I have officially seen this in documentation, however I do seem to recall it working. Tell ya what, let me spin up a handful of machines and see if indeed my memory is correct or not and try your situation and I'll get back with the results.
Children
No Data