Peter Niemayer wrote:
> At least ext2 or fat filesystems on MO-media (that use 2048 sectors)
> never work, mounting such always fails. As it works perfectly on
> the same MO-drives when using media with 512 byte sectors, there has
> to be something wrong...
>
> 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?
>
> While I'm quite familiar with C/gdb etc., I've only very little experience
> with the internal structures used by linux block devices. I could use
> kgdb if necessary... but maybe it's only a simple difference in what
> fsck and mount do to find out the underlying devices block size...
>
> Any idea where to start?
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
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/
