2012/9/13 Lennart Poettering <lenn...@poettering.net>: > On Thu, 30.08.12 21:00, Alexey Shabalin (a.shaba...@gmail.com) wrote: > >> Hello. >> Sorry, i know that swap on lvm bad idea, but ... >> >> systemd-189 used systemd-fstab-generator and lvm2-activation-generator >> (i deleted fedora-storage-init.service and >> fedora-storage-init-late.service). >> >> For test: >> - in fstab: >> UUID=a8ce6981-1afd-4af6-8783-784b3c7a7d64 swap swap >> default 0 0 >> >> after run systemd-fstab-generator i have in /tmp >> dev-disk-by\x2duuid-a8ce6981\x2d1afd\x2d4af6\x2d8783\x2d784b3c7a7d64.swap >> --------------------- >> # Automatically generated by systemd-fstab-generator >> >> [Unit] >> SourcePath=/etc/fstab >> DefaultDependencies=no >> Conflicts=umount.target >> Before=umount.target >> >> [Swap] >> What=/dev/disk/by-uuid/a8ce6981-1afd-4af6-8783-784b3c7a7d64 >> ---------------- >> >> systemctl start >> "dev-disk-by\x2duuid-a8ce6981\x2d1afd\x2d4af6\x2d8783\x2d784b3c7a7d64.swap" >> cannot activate swap, error by timeout. >> but swapon "/dev/disk/by-uuid/a8ce6981-1afd-4af6-8783-784b3c7a7d64" fork >> fine. > > This indicates that the device never showed up as device node in > system. Most likely this is borkage in LVM's udev rules, and should be > reported to that package. > > Please check with "udevadm info > /dev/disk/by-uuid/a8ce6981-1afd-4af6-8783-784b3c7a7d64" if the device is > properly initialized and the systemd tag appears in TAGS=. Only then > systemd will pick it up. > I see TAGS:
P: /devices/virtual/block/dm-1 N: dm-1 E: DEVNAME=/dev/dm-1 E: DEVPATH=/devices/virtual/block/dm-1 E: DEVTYPE=disk E: DM_UDEV_DISABLE_DISK_RULES_FLAG=1 E: DM_UDEV_DISABLE_OTHER_RULES_FLAG=1 E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1 E: MAJOR=253 E: MINOR=1 E: SUBSYSTEM=block E: SYSTEMD_READY=0 E: TAGS=:systemd: E: USEC_INITIALIZED=41372 -- Alexey Shabalin _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
