Re: Long wait for start job

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

 



On Sun, 2021-06-13 at 14:38 -0600, Chris Murphy wrote:
> On Sun, Jun 13, 2021 at 5:26 AM Patrick O'Callaghan
> <pocallaghan@xxxxxxxxx> wrote:
> > 
> > I'm 99% certain it's being caused by my external USB dock starting
> > up.
> > See my reply to Ed. The dock is not mounted at boot, but has a
> > BTRFS
> > filesystem that (possibly) the kernel insists on checking before
> > the
> > rest of the startup can proceed. This is speculation at the moment.
> > 
> > systemd-analyze blame shows a long delay in a unit I created to
> > automatically power down the dock if it's not mounted:
> > 
> > $ systemd-analyze blame|head
> > 4min 18.016s dock-watch.service
> >      30.517s systemd-udev-settle.service
> >      15.273s logrotate.service
> >       6.274s NetworkManager-wait-online.service
> >       5.765s raid.mount
> >       5.452s plymouth-quit-wait.service
> >       5.038s akmods.service
> >       4.541s upower.service
> >       4.427s sssd.service
> > 
> > I've uploaded the dock-watch unit and the scripts it calls,
> > together
> > with the automount unit, to:
> > 
> > https://drive.google.com/drive/folders/1BT5w4u7TzBmWbhx97sWvfOErCIUylrik?usp=sharing
> 
> dock-wait script contains:
> RAID=/dev/sdd
> 
> This may not be reliable because /dev nodes frequently change between
> reboots. You're better off using /dev/disk/by-... any of them are
> better than node. You can use label, uuid, wwn, whatever.
> 
> I actually use a udev rule for idle spin down:
> 
>  $ cat /etc/udev/rules.d/69-hdparm.rules
> ACTION=="add", SUBSYSTEM=="block", \
>   KERNEL=="sd*[!0-9]", \
>   ENV{ID_SERIAL_SHORT}=="WDZ47F0A", \
>   RUN+="/usr/sbin/hdparm -B 100 -S 252 /dev/disk/by-id/wwn-
> 0x5000c500a93cae8a"
> $

Good point. I was already nervous about a hard-wired device name though
it hasn't bitten me so far.

poc
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux