On Thu, Jun 27, 2024 at 11:58:34AM +0100, Leandro Lisboa Penz wrote:
> Package: cryptmount
> Version: 6.2.0-2
> Followup-For: Bug #1072996
>
> Dear Maintainer,
>
> FWIW I am also observing this, but with a slightly different symptom:
>
> $ cryptmount crypted
> e2fsck 1.47.1 (20-May-2024)
> /dev/mapper/crypted: clean, 456/28672 files, 58320/114688 blocks
> [cryptmount-mount]: /home/l/crypted: fsconfig system call failed:
> /dev/mapper/crypted: Can't lookup blockdev.
> dmesg(1) may have more information after failed mount system call.
> unable to stat() device node
> Failed to remove device-mapper target "crypted"
>
> dmesg said only:
>
> [9999.9999] loop2: detected capacity change from 0 to 262144
>
> So the system has been able to detect the size of the device, though it
> still failed.
>
> Adding "flags=nofsck" to cmtab also fixed my case.
...
> -- Configuration Files:
> /etc/cryptmount/cmtab changed:
> syncrypted {
> dev=$(HOME)/crypted.vol
> dir=$(HOME)/crypted
> fstype=auto
> flags=nofsck
> keyformat=luks
> }
Hi,
Seems that this is affecting LUKS systems. I cannot reproduce this in a non
LUKS device I also hace here.
Regards,
--
Agustin
