thin-provisioning-tools not part of lvm?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Why are helper programs required for lvm to use thin provisioning volumes not part of the lvm source package?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRlj5HAAoJEJrBOlT6nu75eJAIAMzgGLClnCntZODqPp5WUxgk 6bbA7JX3cT/NRvSonevAYRp4iYpiyGTUpCpcOgQxFskJBA9Myn0FOXRZmM0kOjWK K6K7nz714X66Tc2qhT1Y8qKqZVh7wqXUunbUsOU3O5LupEgQVgxHel6on98z2zKt o69HaPGHvgt7ubfHvbYdbCr88hZyZUdQuskDPP5LF6kAjXckYjRhN9QAVnH9ThYe Y/h0TONFvqarREBGvcorMR65xgQht4wse5sIMthhVPK1beZh5V+ISpK4Oy7JfF5k uqQB5aXY8OS9yeGriN1/iUYmcpzeq3QjrmHGAopgIZ+UDtczZN/Riy5ny3fjCUE= =vESj
-----END PGP SIGNATURE-----
Quoted 5 lines · Phillip Susi
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Why are helper programs required for lvm to use thin provisioning volumes not part of the lvm source package?
a) Because the whole point of device-mapper is it doesn't tie you in to a single volume manager. Unfortunately EVMS doesn't seem to be developed any more, so LVM2 has become the defacto choice.
b) Because the LVM2 codebase is too big and riddled with closely coupled code that means making any changes takes forever.
- Joe