You are not logged in.
So, I saw a bug report from 2007 regarding a similar occurrence but the solution was to pass unhashed2 or "use dm-crypt/LUKS instead". I figured I'd ask here before/if I post a bug in case I got the same response the previous user did. The thing is that I cannot use unhashed1 or 2 because my partition is encrypted with a random key each time. Here's the fstab entry that's having issues:
/dev/sda6 /tmp reiserfs rw,nodev,nosuid,async,relatime,loop=/dev/loop6,encryption=AES256,phash=random/1777 0 0
util-linux-ng 2.17-1 works fine, but 2.17.1-1 is when the problem occurs. It will prompt for "password:" and since it's random I cannot supply one and so hit <return> and it shows: ioctl: LOOP_SET_STATUS: Invalid argument. and continues on. I can sign in and everything but it causes problems opening Xorg or using anything that requires /tmp as I have to recreate it with proper permissions and on the /root partition which is smaller, not original /tmp disk where it's supposed to be and has quite a bit more space (i use /tmp a lot for various things like dealing with raw images, burning, etc). I cannot find any of my logs that state this ioctl message though I don't guess it matters as it's happened before. I really hope I don't have to force myself to use LUKS in order to use the newest util-linux-ng with my fstab. Anyone else experiencing this or should I file a bug report anyway? Any other information needed, please let me know. Thanks for reading
EDIT: I'll mark this as solved since the answer is: support was dropped. Look at last post for PKGBUILD supporting loop-aes in loop.
Last edited by milomouse (2010-03-24 03:32:32)
Offline
loop-aes support was removed.
Offline
Good job!
Remove the more secure option in favor of upstream politics.
Offline
Really. I guess this means I'm never updating this util-linux-ng again (I'll search out patches, I guess?). I hope this doesn't cause severe problems in the long run because I really like loop-aes and it took me a lot of time and planning to get my partitions (including this laptop, a few external drives, and a small server) the way I want them. Thanks for the links/info, regardless.
Last edited by milomouse (2010-03-13 21:05:46)
Offline
Really. I guess this means I'm never updating this util-linux-ng again (I'll search out patches, I guess?). I hope this doesn't cause severe problems in the long run because I really like loop-aes and it took me a lot of time and planning to get my partitions (including this laptop, a few external drives, and a small server) the way I want them. Thanks for the links/info, regardless.
you could always do a new package utili-linux-ng-aes or smth and upload it in aur.
Give what you have. To someone, it may be better than you dare to think.
Offline
i'm about to go offline for a while but that's not a bad idea. i'll read over the documentation again and see if i can come up with anything
Offline
Ok, so I redid the whole patch just so I knew it would work. Thankfully after using it myself, it works. I tried it on all my loop-aes partitions/drives. 8000+ lines is a lot for me but thankfully it was worth it.
I could edit the fsck-static.patch to be compliant to the changes I've made from previous patch but I don't even know what it does. Do I need it? Here's a link to the patch: github link. It's a little big so may take a second or two to load. Regardless, here's the PKGBUILD I used and I wanted to show it before submitting in case something looks wrong PKGBUILD
So, like I said, this works for me but wanted to check with others before uploading it to the AUR since I've never really had a reason to upload there before. If everything looks ok (fsck-static.patch?) then I'll go ahead an upload for the other people who want loop-aes support. Oh, I had to use the provides=util-linux-ng=2.17.1 only because APR specifies a version specific dependency on it. So, is this ok?
Last edited by milomouse (2010-03-24 03:29:58)
Offline
Well, I uploaded regardless. In case anyone else wants it. http://aur.archlinux.org/packages.php?ID=35887 Still don't know if I should update the fsck-static patch.
Offline