Jari Ruusu wrote: > > During my tests I found that while I can losetup/mkfs/fsck the 2048byte media > > perfectly, a mount afterwards fails. So it seems that while mkfs/fsck never > > try to read something != 2048 byte blocks mount does something based > > on a false sector size assumption. > [snip] > > Ok, so what can I do to help hunting down the cause of the problem? > You could try to set the soft block size of both underlying device and loop > device in question using blockdev utility (it is part of util-linux > package). Something like this: > > blockdev --setbsz 2048 /dev/sda1 > losetup -e AES128 /dev/loop0 /dev/sda1 > blockdev --setbsz 2048 /dev/loop0 > mount -t ext2 /dev/loop0 /mnt I tried this - and many variants just to be sure - but it doesn't help. When using --getbsz to ask for the current block size, the correct value (2048) is returned (for both the loop and the block device). "mount" fails nevertheless... Ok, so what's the next thing to try? :-) Regards, Peter Niemayer - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
