> -----Original Message----- > From: linux-btrfs-owner@xxxxxxxxxxxxxxx [mailto:linux-btrfs- > owner@xxxxxxxxxxxxxxx] On Behalf Of Imran Geriskovan > Sent: Monday, 29 August 2016 9:19 PM > To: Stefan Priebe - Profihost AG <s.priebe@xxxxxxxxxxxx> > Cc: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>; linux-btrfs@xxxxxxxxxxxxxxx > Subject: Re: btrfs and systemd > > >>> I can't find any fstab setting for systemd to higher this timeout. > >>> There's just the x-systemd.device-timeout but this controls how > >>> long to wait for the device and not for the mount command. > >>> Is there any solution for big btrfs volumes and systemd? > >>> Stefan > > Switch to Runit. > > First time I seriously consider another init on my notebook is when I have a > problem like yours. > > Even when / (root) is mounted just fine, if there is any problem with any > other fstab entry, you'll get into such a situation on systemd. > > Give it a try, appending "init=/usr/bin/runit-init" > to your kernel command line on your bootloader. > You dont need to uninstall any package until getting Runit behave "exactly" > as you like. Why not just create a Systemd unit (or whatever the proper term is) that runs on boot and runs the mount command manually and doesn't wait for it to return? Seems easier than messing with init systems. Paul. ��.n��������+%������w��{.n�����{����n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
