[linux-lvm] Reserve space for specific thin logical volumes

Xen list at xenhideout.nl
Sun Sep 17 06:31:36 UTC 2017

Xen schreef op 17-09-2017 0:33:

> But if it's not active, can it still 'trace' another volume? Ie. it
> has to get updated if it is really a snapshot of something right.
> If it doesn't get updated (and not written to) then it also does not
> allocate new extents.

Oh now I get what you mean.

If it's not active it can also in that sense not reserve any extents for 

So the calculations I proposed way below require at least 2 numbers for 
each 'critical' volume to be present in the kernel.

Which is the unallocated virtual size and the reserved space.

So even if they're not active they would need to provide this 
information somehow.

Of course the information also doesn't change if it's not active, so it 
would just be 2 static numbers.

But then what happens if you change the reserved space etc...

In any case that sorta thing would indeed be required...

(For an in-kernel thing...)

(Also any snapshot of a critical volume would not in itself become a 
critical volume...)

(But you're saying that "thin snapshot" is not a kernel concept...)

More information about the linux-lvm mailing list