Summary: | losetup regression: ceased to support the "size"-parameter | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Guenther Brunthaler <gb_about_gnu> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | VERIFIED INVALID | ||
Severity: | critical | CC: | gb_about_gnu |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Guenther Brunthaler
2008-04-02 19:22:43 UTC
I have tagged this issue as "critical" rather than "major", because it can result in data corruption. I suggest *immediately* re-masking of the new sys-apps/util-linux versions until the issue is resolved! This will at least avoid data loss for the affected installations. Regarding my idea of using the device mapper instead of losetup, there is a problem with this: Nearly every kernel has support for losetup compiled in, but not all kernels have been built with device mapper support. As a consequence, all those installations will either have to mask all new util-linux versions since the regression was introduced, or have to recompile the kernel with device mapper support enabled. I know genkernel has dm-support enabled, but a lot of admins prefer to set up their own kernel configurations. And even if dm-support is enabled, one has first to find a way to emulate losetup's old behaviour using dmsetup. Which might or might not be fun... ;-) you didnt add loop-aes to your USE (In reply to comment #4) > you didnt add loop-aes to your USE You are right. But then, I never did, and "-s" still worked until the new version. Also, my use flag description says: sys-apps/util-linux:loop-aes - include support for Loop AES encryption There is no hint that it is also required for mounting *unencrypted* partitions out of unencrypted disk images. Also, my kernel does not have any AES support enabled, because I'm using TrueCrypt rather than aes-loop. (This allows me to use the same disk images under Linux as well as under that other operating system which is primarily designed for playing games.) But nevertheless, thanks for the hint - I will immediately re-emerge util-linux with loop-aes enabled and will see whether it helped! OK - verified! I also noted that little message when compiling: * USE=crypt has been changed to USE=loop-aes. If you need * support for it, make sure to update your USE accordingly. and indeed - I have had USE flag "crypt" enabled until now, but never "loop-aes". This message thus explains the regression! I didn't notice because it was just a "green" message, not a yellow one. Actually it should have been red and blinking... ;-) Nevertheless: Issue resolved. Thanks for your swift reaction! Closing bug. |