Peter Niemayer wrote: > I tried with kernel 2.4.18 and loop-AES-1.6b. [snip] > Any idea? Strace output didn't help: I wanted to see that mount() system call parameters were sane... and they were sane. Were there any kernel error messages? You can display them with "dmesg" command and they probably are also archived at /var/log/messages file. Can you modify your test script so that mkfs always creates filesystem with 2 KB soft block size (mkfs -t ext2 -b 2048 /dev/loop0), and that it displays the soft block size of both /dev/sdb (blockdev --getbsz /dev/sdb) and /dev/loop0 (blockdev --getbsz /dev/loop0) _after_ failed mount attempt? Regards, Jari Ruusu <jari.ruusu@pp.inet.fi> - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
