Stric allocation policy

[M. Tariq Ayub]

When i tried to inctrase a lvol it says strick allocation policy. How to disable it.

[A. Clay Stephenson]

You can't. The allocation policy is set when the logical volume is created. You would have to do an lvremove then an lvcreate after first backing up your data.

Some LVOL's MUST be contigious and thus must be under strict allocation (e.g. /stand, device swap LVOL's, and /); if you need to extend those LVOL's then it's time to use Ignite/UX and make_tape_recovery to rebuild your OS.

[M. Tariq Ayub]

can we use lvchamve -s n to remove restriction.

[A. Clay Stephenson]

Yes, I should have been a little bit more specific. Lvchange can be used BUT ONLY if you know the operation is safe. For example, you can use lvchange to alter /stand (or /) to not be strictly allocated and you will kill your system. The bad news is that you might alter / and things would APPEAR to be okay for a while. If you KNOW that the LVOL isa question does not require strict allocation then you can turn it off. Again, /stand, /, and any device swap lvol must remain strictly allocated but they can and should be mirrored -- if you have Mirror/UX.

[Kevin Wright]

lvchange -s n will work, as long as your sure you will not be mirroring pv to pv's on the same disk!

[Steven E. Protter]

You can't use lvchange in swap, / (root) and /stand because they require strict allocation.

Beyond that, you can do it. I've tried it a few times on my sandbox. The fact that it exists should not substitute for good disk layout planning.

SEP