On Thu, 13 Jun 2019, Andreas Schwab wrote: > On Jun 13 2019, Finn Thain <[email protected]> wrote: > > > IMHO these log messages are a bit silly -- > > > > [ **] (3 of 3) A start job is running for /dev/sda4 (1min 5s / 1min 36s) > > ... > > [ TIME ] Timed out waiting for device /dev/sda4. > > [DEPEND] Dependency failed for /dev/sda4. > > [DEPEND] Dependency failed for Swap. > > ... > > Activating swap /dev/sda4... > > ... > > [ 450.650000] Adding 524284k swap on /dev/sda4. Priority:-2 extents:1 > > across:524284k FS > > ... > > [ OK ] Activated swap /dev/sda4. > > That just means that the timeout is maybe too short,
Adding swap isn't that complicated. If you have you swap partition on MD RAID ROCE, I'd hazard a guess that you aren't using Linux/m68k for that. This is a use-case that systemd should probably cater to. But making everyone pay for that complexity is poor design IMHO. > but if a device is showing up late it is handled like hotplug and works > anyway. > The device isn't late, swapon() is late (compared to Debian 3 or Debian 4). [ 206.380000] sda: [mac] sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 ... [ 206.790000] sd 0:0:0:0: [sda] Attached SCSI disk ... [ 243.400000] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) -- > Andreas. >
