You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use LVM on my system, so my crypt device is /dev/mapper/vgcrypt and the root filesystem is actually mounted on /dev/mapper/vgcrypt-root. Here's my /proc/cmdline:
The arch-luks-suspend script temporarily remounts ext4 filesystems with barrier=0, but it looks for a mounted filesystem in /dev/mapper/${CRYPTNAME}, which isn't necessarily the root filesystem's device. Instead, I think it should use the value of root in /proc/cmdline. I'll submit a PR shortly.
The text was updated successfully, but these errors were encountered:
afn
added a commit
to afn/arch-luks-suspend
that referenced
this issue
Dec 30, 2016
cf. #1
In an LVM on LUKS setup the root cryptdevice does not hold the
filesystem that is mounted on /. We can get this information from
/proc/cmdline instead.
Credit to afn:
vianney#8
I use LVM on my system, so my crypt device is
/dev/mapper/vgcrypt
and the root filesystem is actually mounted on/dev/mapper/vgcrypt-root
. Here's my/proc/cmdline
:The
arch-luks-suspend
script temporarily remounts ext4 filesystems withbarrier=0
, but it looks for a mounted filesystem in/dev/mapper/${CRYPTNAME}
, which isn't necessarily the root filesystem's device. Instead, I think it should use the value ofroot
in/proc/cmdline
. I'll submit a PR shortly.The text was updated successfully, but these errors were encountered: