On Sun, 2013-07-21 at 13:45 +0100, Sam Morris wrote: > On Sun, 2013-07-21 at 13:42 +0200, Michael Stapelberg wrote: > > Hi Sam, > > > > Reading https://bugzilla.redhat.com/show_bug.cgi?id=759402 (especially > > comment #15) I suspect the issue is that systemd is not getting notified > > about the swap device properly. Can you please run > > > > udevadm info -q all -n /dev/mapper/swap0 > > P: /devices/virtual/block/dm-0 > N: dm-0 > L: 50 > S: disk/by-id/dm-name-swap0 > S: disk/by-id/dm-uuid-CRYPT-PLAIN-swap0 > S: mapper/swap0 > E: DEVLINKS=/dev/disk/by-id/dm-name-swap0 > /dev/disk/by-id/dm-uuid-CRYPT-PLAIN-swap0 /dev/mapper/swap0 > E: DEVNAME=/dev/dm-0 > E: DEVPATH=/devices/virtual/block/dm-0 > E: DEVTYPE=disk > E: DM_NAME=swap0 > E: DM_STATE=ACTIVE > E: DM_SUSPENDED=0 > E: DM_TABLE_STATE=LIVE > E: DM_TYPE=raid > E: DM_UDEV_PRIMARY_SOURCE_FLAG=1 > E: DM_UDEV_RULES=1 > E: DM_UUID=CRYPT-PLAIN-swap0 > E: MAJOR=254 > E: MINOR=0 > E: SUBSYSTEM=block > E: SYSTEMD_READY=0 > E: TAGS=:systemd: > E: USEC_INITIALIZED=945279 > E: net.ifnames=1 > > > cat /proc/sys/kernel/hotplug > > This is just an empty line. > > > and provide the output here? > > I'm guessing SYSTEMD_READY=0 is the suspicious entry.
FYI, my system originally only had udisks2 installed, not udisks. I
installed udisks (so that both are now installed) and rebooted, and the
swap device is now set up properly.
udevadm info now says,
P: /devices/virtual/block/dm-0
N: dm-0
L: 50
S: disk/by-id/dm-name-swap0
S: disk/by-id/dm-uuid-CRYPT-PLAIN-swap0
S: disk/by-uuid/02331091-93b9-46e3-827b-4d940df2159e
S: mapper/swap0
E: DEVLINKS=/dev/disk/by-id/dm-name-swap0
/dev/disk/by-id/dm-uuid-CRYPT-PLAIN-swap0
/dev/disk/by-uuid/02331091-93b9-46e3-827b-4d940df2159e /dev/mapper/swap0
E: DEVNAME=/dev/dm-0
E: DEVPATH=/devices/virtual/block/dm-0
E: DEVTYPE=disk
E: DM_NAME=swap0
E: DM_STATE=ACTIVE
E: DM_SUSPENDED=0
E: DM_TABLE_STATE=LIVE
E: DM_TYPE=raid
E: DM_UDEV_PRIMARY_SOURCE_FLAG=1
E: DM_UDEV_RULES=1
E: DM_UUID=CRYPT-PLAIN-swap0
E: ID_FS_TYPE=swap
E: ID_FS_USAGE=other
E: ID_FS_UUID=02331091-93b9-46e3-827b-4d940df2159e
E: ID_FS_UUID_ENC=02331091-93b9-46e3-827b-4d940df2159e
E: ID_FS_VERSION=2
E: MAJOR=254
E: MINOR=0
E: SUBSYSTEM=block
E: TAGS=:systemd:
E: UDISKS_DM_TARGETS_COUNT=1
E: UDISKS_DM_TARGETS_LENGTH=4192223
E: UDISKS_DM_TARGETS_START=0
E: UDISKS_DM_TARGETS_TYPE=crypt
E: UDISKS_PRESENTATION_NOPOLICY=1
E: USEC_INITIALIZED=24880
E: net.ifnames=1
i.e., SYSTEMD_READY is no longer there, which I believe implicitly means
that it's set to 1.
--
Sam Morris <https://robots.org.uk/>
3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
signature.asc
Description: This is a digitally signed message part
