Re: F24: systemd fails to mount 128 LVM partitions. (udev issue?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jul 28, 2016 at 6:07 AM, Zbigniew Jędrzejewski-Szmek
<zbyszek@xxxxxxxxx> wrote:
>
> It is possible that udevd is failing for whatever reason... but apart
> from the fact that some of the devices links are missing you don't
> provide any info. At the minimum: boot logs, and information which links
> are missing.

Boot log info is pretty scarce. I only see a lot of systemd timed-out
log messages:
E.g.

systemd[1]: dev-VolRoot-LogStorageMData_P123.device: Job
dev-VolRoot-LogStorageMData_P123.device/start timed out.
systemd[1]: dev-VolRoot-LogStorageMData_P125.device: Job
dev-VolRoot-LogStorageMData_P125.device/start timed out.
systemd[1]: dev-VolRoot-LogStorageMData_P124.device: Job
dev-VolRoot-LogStorageMData_P124.device/start timed out.
systemd[1]: dev-VolRoot-LogStorageMData_P122.device: Job
dev-VolRoot-LogStorageMData_P122.device/start timed out.
systemd[1]: dev-VolRoot-LogStorageMData_P127.device: Job
dev-VolRoot-LogStorageMData_P127.device/start timed out.
systemd[1]: dev-VolRoot-LogStorageMData_P123.device: Job
dev-VolRoot-LogStorageMData_P123.device/start timed out.
systemd[1]: dev-VolRoot-LogStorageMData_P126.device: Job
dev-VolRoot-LogStorageMData_P126.device/start timed out.

I did see some udev / LVM error messages:
systemd-udevd[2181]: fork of '/usr/sbin/dmsetup splitname
--nameprefixes --noheadings --rows VolRoot-LogStorageMData_P96'
failed: Resource temporarily unavailable

Either way, I've attached a boot log.

> Note that just running the generator by hand has no effect. You need
> systemctl daemon-reload to reload the units, but that will re-run the
> generators by itself.

Just to be certain: Changing fstab requires systemctl daemon-reload?

>
> I'd suggest commenting out (or adding "noauto") the mount points in /etc/fstab,
> (and of course also disabling any units which make use of them if they are
> not conditionalized), and debugging in a booted system. It's most likely to
> be easier this way.
>

The attached log seems to suggest this indeed a udev/lvm issue.
Thanks for taking the time to help :)

- Gilboa

Attachment: boot.log.bz2
Description: BZip2 compressed data

--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux