Summary: | >=sys-fs/lvm2-2.02.184 - systemd[1]: Timed out waiting for device /dev/mapper/gentoo-swap. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mariusz Ceier <mceier> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | adrian, agk, cardoe, joakim.tjernlund, robbat2, zoltan |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=682578 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mariusz Ceier
2019-05-01 14:01:27 UTC
`systemctl mask lvm2-monitor.service` fixes it for me, thanks to helpful viewer from random YT livestream. That workaround doesn't work anymore... ffs, how hard is to do "swapon -a" I'm experiencing the same problem, except it started with >=sys-fs/lvm2-2.02.187. I noticed lvmetad is disabled on 2.02.187 and later. I've also confirmed when you're on 2.02.184, and you set use_lvmetad = 0, you get the same problem as 2.02.187. So, disabling lvmetad seems to be a part of the problem, though I don't think this is the root of the problem. (In reply to vax456 from comment #3) > I'm experiencing the same problem, except it started with > >=sys-fs/lvm2-2.02.187. > > I noticed lvmetad is disabled on 2.02.187 and later. I've also confirmed > when you're on 2.02.184, and you set use_lvmetad = 0, you get the same > problem as 2.02.187. > > So, disabling lvmetad seems to be a part of the problem, though I don't > think this is the root of the problem. In /etc/lvm/lvm.conf I have use_lvmetad=1 and I don't remember ever changing it. The bug is still present with sys-fs/lvm2-2.02.187-r2 and as a "workaround" I just removed swap from /etc/stab, since I have 32GB of ram. My partitions look like this (part of lsblk output): sdb 8:16 0 119,2G 0 disk └─sdb4 8:20 0 118G 0 part ├─gentoo-swap 253:0 0 15,8G 0 lvm ├─gentoo-home 253:1 0 1,9T 0 lvm / └─gentoo-root 253:2 0 50G 0 lvm I have no idea what's the root of the problem (except if only systemd were executing "swapon -a" instead of reimplementing everything itself there wouldn't be a problem). I am having the same problem, the machine adds my root which is on the same (LUKS) LVM vg as the swap file, but after mounting everything else, it waits for 1m30s for the swap to activate before timing out and continuing. The 'funny' thing is that there is no trace of that attempted mount in the genkernel-boot.log or in dmesg, so I don't know what's going on. Am using 2.02.187-r2. As soon as I am done booting, I can just do a swapon /dev/vg_sys/swap and everything works just fine. Same problem for me. Would really like to know WTF is causing this, and how to avoid it (besides not using swap or not using fstab to enable swap automatically) As I'm using a slightly more split up layout this is causing me more trouble: Aug 08 12:01:48 speedie systemd[1]: dev-ssdforce-portage.device: Job dev-ssdforce-portage.device/start timed out. Aug 08 12:01:48 speedie systemd[1]: Timed out waiting for device /dev/ssdforce/portage. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for File System Check on /dev/ssdforce/portage. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for /var/tmp/portage. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for Local File Systems. Aug 08 12:01:48 speedie systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. Aug 08 12:01:48 speedie systemd[1]: var-tmp-portage.mount: Job var-tmp-portage.mount/start failed with result 'dependency'. Aug 08 12:01:48 speedie systemd[1]: systemd-fsck@dev-ssdforce-portage.service: Job systemd-fsck@dev-ssdforce-portage.service/start failed w> Aug 08 12:01:48 speedie systemd[1]: dev-ssdforce-portage.device: Job dev-ssdforce-portage.device/start failed with result 'timeout'. Aug 08 12:01:48 speedie systemd[1]: dev-hddgen-media.device: Job dev-hddgen-media.device/start timed out. Aug 08 12:01:48 speedie systemd[1]: Timed out waiting for device /dev/hddgen/media. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for /srv/media. Aug 08 12:01:48 speedie systemd[1]: srv-media.mount: Job srv-media.mount/start failed with result 'dependency'. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for File System Check on /dev/hddgen/media. Aug 08 12:01:48 speedie systemd[1]: systemd-fsck@dev-hddgen-media.service: Job systemd-fsck@dev-hddgen-media.service/start failed with resu> Aug 08 12:01:48 speedie systemd[1]: dev-hddgen-media.device: Job dev-hddgen-media.device/start failed with result 'timeout'. Aug 08 12:01:48 speedie systemd[1]: dev-hddgen-var.device: Job dev-hddgen-var.device/start timed out. Aug 08 12:01:48 speedie systemd[1]: Timed out waiting for device /dev/hddgen/var. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for File System Check on /dev/hddgen/var. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for /var. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for Update UTMP about System Runlevel Changes. Aug 08 12:01:48 speedie systemd[1]: systemd-update-utmp-runlevel.service: Job systemd-update-utmp-runlevel.service/start failed with result> Aug 08 12:01:48 speedie systemd[1]: Dependency failed for Network Time Synchronization. Aug 08 12:01:48 speedie systemd[1]: systemd-timesyncd.service: Job systemd-timesyncd.service/start failed with result 'dependency'. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for Flush Journal to Persistent Storage. Aug 08 12:01:48 speedie systemd[1]: systemd-journal-flush.service: Job systemd-journal-flush.service/start failed with result 'dependency'. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for /var/tmp. Aug 08 12:01:48 speedie systemd[1]: var-tmp.mount: Job var-tmp.mount/start failed with result 'dependency'. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for Update UTMP about System Boot/Shutdown. Aug 08 12:01:48 speedie systemd[1]: systemd-update-utmp.service: Job systemd-update-utmp.service/start failed with result 'dependency'. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for Load/Save Random Seed. Aug 08 12:01:48 speedie systemd[1]: systemd-random-seed.service: Job systemd-random-seed.service/start failed with result 'dependency'. Aug 08 12:01:48 speedie systemd[1]: var.mount: Job var.mount/start failed with result 'dependency'. Aug 08 12:01:48 speedie systemd[1]: systemd-fsck@dev-hddgen-var.service: Job systemd-fsck@dev-hddgen-var.service/start failed with result '> Aug 08 12:01:48 speedie systemd[1]: dev-hddgen-var.device: Job dev-hddgen-var.device/start failed with result 'timeout'. Aug 08 12:01:48 speedie systemd[1]: dev-hddgen-vartmp.device: Job dev-hddgen-vartmp.device/start timed out. Aug 08 12:01:48 speedie systemd[1]: Timed out waiting for device /dev/hddgen/vartmp. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for File System Check on /dev/hddgen/vartmp. Aug 08 12:01:48 speedie systemd[1]: systemd-fsck@dev-hddgen-vartmp.service: Job systemd-fsck@dev-hddgen-vartmp.service/start failed with re> Aug 08 12:01:48 speedie systemd[1]: dev-hddgen-vartmp.device: Job dev-hddgen-vartmp.device/start failed with result 'timeout'. Aug 08 12:01:48 speedie systemd[1]: dev-hddgen-usrsrc.device: Job dev-hddgen-usrsrc.device/start timed out. Aug 08 12:01:48 speedie systemd[1]: Timed out waiting for device /dev/hddgen/usrsrc. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for File System Check on /dev/hddgen/usrsrc. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for /usr/src. Aug 08 12:01:48 speedie systemd[1]: usr-src.mount: Job usr-src.mount/start failed with result 'dependency'. Aug 08 12:01:48 speedie systemd[1]: systemd-fsck@dev-hddgen-usrsrc.service: Job systemd-fsck@dev-hddgen-usrsrc.service/start failed with re> Aug 08 12:01:48 speedie systemd[1]: dev-hddgen-usrsrc.device: Job dev-hddgen-usrsrc.device/start failed with result 'timeout'. Aug 08 12:01:48 speedie systemd[1]: dev-ssdforce-opt.device: Job dev-ssdforce-opt.device/start timed out. Aug 08 12:01:48 speedie systemd[1]: Timed out waiting for device /dev/ssdforce/opt. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for File System Check on /dev/ssdforce/opt. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for /opt. Aug 08 12:01:48 speedie systemd[1]: opt.mount: Job opt.mount/start failed with result 'dependency'. Aug 08 12:01:48 speedie systemd[1]: systemd-fsck@dev-ssdforce-opt.service: Job systemd-fsck@dev-ssdforce-opt.service/start failed with resu> Aug 08 12:01:48 speedie systemd[1]: dev-ssdforce-opt.device: Job dev-ssdforce-opt.device/start failed with result 'timeout'. Aug 08 12:01:48 speedie systemd[1]: dev-hddgen-portage.device: Job dev-hddgen-portage.device/start timed out. Aug 08 12:01:48 speedie systemd[1]: Timed out waiting for device /dev/hddgen/portage. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for File System Check on /dev/hddgen/portage. Aug 08 12:01:48 speedie systemd[1]: Dependency failed for /usr/portage. attempting to mount the paths manually succeed but the filesystem doesn't actually appear. Instead I have to run pvscan vgscan --mknodes vgchange --sysinit -a ly After which point I can now see files appear when I mount the filesystems though the names generated by mapper point to the wrong devices and I have to work out the correct filesystem to mount onto the various paths in order for the systemd jobs to all succeed subsequently. Looking through the journal log output subsequently I see the following messages appear Aug 08 12:10:23 speedie systemd-udevd[4412]: dm-0: Conflicting device node '/dev/mapper/ssdforce-opt' found, link to '/dev/dm-0' will not be created. Aug 08 12:10:23 speedie systemd-udevd[4412]: dm-1: Conflicting device node '/dev/mapper/ssdforce-portage' found, link to '/dev/dm-1' will not be created. Aug 08 12:10:24 speedie systemd-udevd[4432]: dm-7: Conflicting device node '/dev/mapper/hddgen-usrsrc' found, link to '/dev/dm-7' will not be created. Aug 08 12:10:24 speedie systemd-udevd[4413]: dm-8: Conflicting device node '/dev/mapper/hddgen-media' found, link to '/dev/dm-8' will not be created. Aug 08 12:10:24 speedie systemd-udevd[4412]: dm-2: Conflicting device node '/dev/mapper/hddgen-portage' found, link to '/dev/dm-2' will not be created. Aug 08 12:10:24 speedie systemd-udevd[4415]: dm-3: Conflicting device node '/dev/mapper/hddgen-var' found, link to '/dev/dm-3' will not be created. Aug 08 12:10:24 speedie systemd-udevd[4428]: dm-4: Conflicting device node '/dev/mapper/hddgen-vartmp' found, link to '/dev/dm-4' will not be created. I suspect these are the reason that I end up with the wrong devices getting mounted when I attempt to use the default names, unclear currently whether that is due to me running one of the commands above or they were generated incorrectly during the boot up. Downgrading to a local ebuild of =sys-fs/lvm2-2.02.184-r5 that I copied out of the gentoo repository history is sufficient to have me booting normally again. I'm guessing the timeout that we're seeing is due to /dev/mapper/* not pointing to the correct device node and consequently the expected device/filesystem it should reference not being found. What I don't know is why? Is it a bug with the newer versions of lvm2 or some stale configuration/files that is not expected by newer lvm2 causing the behaviour. Just started to test out systemd at work and we got this far too. There is something odd with crypto/lvm2. Without crypto(only lvm2) is fine |