On Thu, Jul 28, 2016 at 03:41:38PM +0300, Gilboa Davara wrote: > On Thu, Jul 28, 2016 at 3:23 PM, Tomasz Torcz <tomek@xxxxxxxxxxxxxx> wrote: > > On Thu, Jul 28, 2016 at 03:04:12PM +0300, Gilboa Davara wrote: > >> 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 > > > > Hm, do you have TasksMax=infinity in systemd-udevd.service? > > (commit de2edc008a612e152f0690d5063d53001c4e13ff) > > > > Nope. I don't see TasksMax in systemd-udevd.service. systemd added a default limit for TasksMax. TasksMax=infinity undoes that limit for systemd-udev. I now built //koji.fedoraproject.org/koji/taskinfo?taskID=15052388 with that patch applied for F24. > Actually, funny that you mention it. (Maybe the following will help others) > I use the server to run some type of proprietary service that spawns > ~2000+ process. This service stopped working the second I switched to > F24. > After spending a couple of hours banging my head against the wall, I > noticed that systemd is ignoring the service user's limits.d nproc > limit (also the service unit's LimitNPROC limit) preventing it from > forking more than 256 process. > Adding TasksMax=infinity to the service's unit solved the problem. > > Related? Most likely. Zbyszek -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
