
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have an encripted filesystem inherited from 10.2 and before. I have this line in fstab: /biggy/crypta_f.mm.x /mnt/crypta.mm.x xfs noauto,user,noatime,nodiratime,loop,encryption=twofish256 1 4 Reading from this filesystem works (I'm copying it elsewhere now). Writing to this filesystem, from another similarly encripted filesystem, large files (between 300 and 400 MB), locks the console where the copy is having place. The copy process stops. It is unkillable. Umount of that filesystem locks (and umount is unkillable). Reboot filesystem locks. If I try to "ls -l" the destination dir of the copy (that is locked, frozen) also freezes. I have to lazy umount ("umount -l /mountpoints &") all the mountpoints I can, and then try to reboot (which hangs) and then poweroff the machine forcefully. There is absolutely nothing in the logs relative to this problem (I know how to look into logs). I have fsck the filesystem, nothing: nimrodel:~ # losetup -e twofish256 /dev/loop2 /biggy/crypta_f.mm.x Password: nimrodel:~ # file -s /dev/loop2 /dev/loop2: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs) nimrodel:~ # xfs_check /dev/loop2 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_check. If you are unable to mount the filesystem, then use the xfs_repair -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. nimrodel:~ # mount /dev/loop2 /mnt/crypta.mm.x/ nimrodel:~ # umount /dev/loop2 nimrodel:~ # xfs_check /dev/loop2 nimrodel:~ # No errors. I'm aware that the encription filesystems have changed in 10.3, but the only document I have is the release notes. Probably I would have to use a different method than losetup, but I have no idea which. An encripted filesystem I see it uses devmap. But notice that the problem arises from a filesystem mounted directly from fstab - shouldn't this method be used now anymore? In any case, the "classic" method should freeze the computer, as it does :-? - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHTiu2tTMYHG2NR9URAr5gAJwNybIdLLBs5NTiirEehsYUOUzKOwCeN0s3 +FOv7HWC2FOfojUrCKae3r4= =WgTn -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org