On 2016-08-29 07:18, Imran Geriskovan wrote:
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.
I hate to say this, but based on my own experience, I have to say that
switching to a different init system is usually the simplest and
quickest solution to almost any 'systemd does X that I don't like' problems.
I can't personally give any advice on runit as I've never used it
myself, but I can say that the stack I'm using (sysv-init, OpenRC, and
monit) provides most of the good things about systemd except for socket
activation and interruptible parallel startup, and it's not hard to get
similarly complete configurations with other tools too.
The downside to this of course is that there are some projects that
shouldn't need to depend on a particular init system that do, so some
software may need to be replaced on your system.
As far as this specific case, mount units are what you want to look
into, as mentioned by Duncan.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
