On Fri, Jul 24, 2015 at 1:37 PM, Vincent Olivier <vincent@xxxxxxx> wrote: > On Jul 24, 2015, at 3:27 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > I'm not sure if its a systemd bug, a udev bug, or a btrfs device scan > bug, or a fast boot with slow spin up of the drives in the Btrfs. > > This system doesn't boot from this 12 disk Btrfs, correct? > > Most exact, yes. > > > > > You could try changing fstab mount options to include: > noauto,x-systemd.automount > > I did and it worked. Isn’t it a tad ugly though ? No. The noauto is appropriate because you don't want this volume to cause basic.target to fail. By using noauto, the volume isn't added to local-fs.target. You could experiment with x-systemd.device-timeout= but that's just going to cause your boot to delay waiting for it; and I'm not sure it'll actually work. You may have to iterate. > Mount time is very close to 10 seconds which is quite high I think, no ? Well that's a Btrfs thing, and it sounds like right now that's normal for a volume of this size. Since it has to find all the devices, read their superblocks, make sure the fs is minimally consistent, it doesn't sound too bad. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
