Fran ois:
> I confirm it's actually my issue. I use loop-aes v3.7a downloaded there:
>
> http://loop-aes.sourceforge.net/loop-AES/
>
> But "aufs3-loopback.patch" doesn't apply well on the modified loop.c
> from loop-aes.
Ok, now I can sleep well. :-)
> Do you have another patch for loop-aes support? I can try to adapt the
> current one if you think there is a chance that it might work.
There is one thing I noticed during the discussion.
For your case, I suppose aufs3-loopback.patch is unnecessary.
Because you have mounted
> 1. /dev/sr0 mounted on /live/image
> 2. /live/image/live/filesystem.squashfs "looped" on /dev/loop0
> 3. /dev/loop0 mounted on /filesystem.squashfs
> 4. tmpfs mounted on /cow
which means "loop0" kthread accesses filesystem.squashfs directly,
instead of via aufs.
aufs3-loopback.patch is to support the case where the fs-image file
exists inside aufs. For example,
- /u = /rw + /ro
- mount -o loop /u/fs.img /ro2
- mount -o remount,append=/ro2 /u
In this case, "loopN" kthread will access "/u/fs.img" which is inside
aufs. Aufs has to handle this as a special case and aufs3-loopback.patch
will do that. If you don't apply aufs3-loopback.patch, aufs will print a
message
pr_warn("you may want to try another patch for loopback file "
"on %s(0x%lx) branch\n", au_sbtype(h_sb), magic);
In other words, you don't need aufs3-loopback.patch until you see this
msg.
So I'd suggest you to try
- stop applying aufs3-loopback.patch
- use loop-aes as is
J. R. Okajima
------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends. Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
