Zdenek Kabelac schreef op 12-09-2017 14:03:
Unfortunatelly lvm2 nor dm can be responsible for whole kernel logic
and
all user-land apps...
What Gionatan also means, or at least what I mean here is,
If functioning is chain and every link can be the weakest link.
Then sometimes you can build in a little redundancy so that other weak
links do not break so easily. Or that your part can cover it.
Linux has had a mindset of reducing redundancy lately. So every bug
anywhere can break the entire thing.
Example was something I advocated for myself.
I installed GRUB2 inside PV reserved space.
That means 2nd sector had PV, 1st sector had MBR-like boot sector.
libblkid stopped at MBR and did not recognise PV.
Now because udev required libblkid to recognise PVs it did not recognise
and did not activate it.
Problem.
Weakest link in this case libblkid.
Earlier vgchange -ay worked flawlessly (and had some redundancy) but was
no longer used.
So you can see how small things can break entire system. Not good
design.
Firmware RAID signature at end of drive also breaks system.
Not good design.
You can also minimize amount of 'dirty' pages to avoid loosing too much
data
in case you hit full thin-pool unexpectedly.....
Torvalds advocated this.
You can sync every second to minimize amount of dirty pages....
Lots of things.... all of them will in some other the other impact
system performance....
He said no people would be hurt by such a measure except people who
wanted to unpack and compile kernel pure in page buffers ;-).
_______________________________________________
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/
