On Fri, Feb 05, 2016 at 16:08:28 CET, Robert Nichols wrote: > On 02/04/2016 11:23 AM, Arno Wagner wrote: > >On the other hand, resizing a Luks container with a > >filesystem in there without killing that filesystem is > >already complicated enough that I usually just recomend > >a backup and recreation instead of a resize. > > Making an already difficult process more complex isn't going to > win many friends. Sounds like what you need is a "--resizefs" > option like the one LVM's lvresize uses to invoke fsadm(8). And thereby limit what filesystem can be in there? That is a rather gross layering-violation and not a good idea. Do not forget that backup and restore need to be tested and the backup done regularly anyways if the data has any worth. I an not asking people to do anything new. (Well, except for those with only throwaway-data in their encrypted containers....) Regards, Arno -- Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@xxxxxxxxxxx GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718 ---- A good decision is based on knowledge and not on numbers. -- Plato If it's in the news, don't worry about it. The very definition of "news" is "something that hardly ever happens." -- Bruce Schneier _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
