Zdenek Kabelac schreef op 23-04-2017 11:26:
I'm just currious - what the you think will happen when you have
root_LV as thin LV and thin pool runs out of space - so 'root_LV'
is replaced with 'error' target.
Why do you suppose Root LV is on thin?
Why not just stick to the common scenario when thin is used for extra
volumes or data?
I mean to say that you are raising an exceptional situation as an
argument against something that I would consider quite common, which
doesn't quite work that way: you can't prove that most people would not
want something by raising something most people wouldn't use.
I mean to say let's just look at the most common denominator here.
Root LV on thin is not that.
I have tried it, yes. Gives troubles with Grub and requires thin package
to be installed on all systems and makes it harder to install a system
too.
Thin root LV is not the idea for most people.
So again, don't you think having data volumes produce errors is not
preferable to having the entire system hang?
How do you think this will be ANY different from hanging your system ?
Doesn't happen cause you're not using that.
You're smarter than that.
So it doesn't happen and it's not a use case here.
IMHO reboot is still quite fair solution in such case.
That's irrelevant; if the thin pool is full you need to mitigate it,
rebooting won't help with that.
And if your root is on thin, rebooting won't do you much good either. So
you had best keep a running system in which you can mitigate it live
instead of rebooting to avail.
That's just my opinion and a lot more commonsensical than what you just
said, I think.
But to each his own.
_______________________________________________
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/
