Dne 13.4.2017 v 15:52 Xen napsal(a):
Stuart Gathman schreef op 13-04-2017 14:59:
If you are going to keep snapshots around indefinitely, the thinpools
are probably the way to go. (What happens when you fill up those?
Hopefully it "freezes" the pool rather than losing everything.)
My experience is that the system crashes.
I have not tested this with a snapshot but a general thin pool overflow
crashes the system.
Within half a minute, I think.
It is irrelevant whether the volumes had anything to do with the operation of
the system; ie. some mounted volumes that you write to that are in no other
use will crash the system.
Hello
Just let's repeat.
Full thin-pool is NOT in any way comparable to full filesystem.
Full filesystem has ALWAYS room for its metadata - it's not pretending it's
bigger - it has 'finite' space and expect this space to just BE there.
Now when you have thin-pool - it cause quite a lot of trouble across number of
layers. There are solvable and being fixed.
But as the rule #1 still applies - do not run your thin-pool out of space - it
will not always heal easily without losing date - there is not a simple
straighforward way how to fix it (especially when user cannot ADD any new
space he promised to have)
So monitoring pool and taking action ahead in time is always superior solution
to any later postmortem systems restores.
Regards
Zdenek
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
