Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Philip Seeger <p0h0i0l0i0p@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: systemd : Timed out waiting for defice dev-disk-by…
Date: Mon, 27 Jul 2015 21:16:38 +0200	[thread overview]
Message-ID: <55B68396.1030505@googlemail.com> (raw)
In-Reply-To: <pan$a902b$10dd7fbd$f0ca0693$dc0cc8e3@cox.net>

On 07/27/2015 07:20 AM, Duncan wrote:
> Philip Seeger posted on Sun, 26 Jul 2015 22:39:04 +0200 as excerpted:
>
>> Hi,
>>
>>> 50% of the time when booting, the system go in safe mode because my 12x
>>> 4TB RAID10 btrfs is taking too long to mount from fstab.
>>
>> This won't help, but I've seen this exact behavior too (some time ago).
>> Except that it wasn't 50% that it didn't work, more like almost
>> everytime.
>> Commenting out the fstab entry "fixed" it, mounting using a cronjob
>> (@reboot) worked without a problem.
>>
>> (As far as I remember, options like x-systemd.device-timeout didn't
>> change anything.)
>>
>> If someone has the answer, I'd be interested too.
>
> You mean something like a custom systemd *.service unit file?  That's
> what I'd do here. =:^)
> [...]

Thanks for the tip and the detailed explanation. I believe I have tried 
something similar back then (involving a custom systemd service), but 
it's too long ago, I can't tell for sure. What I do remember clearly is 
that the timeout error came within seconds after invoking the mount 
command, maybe 5 or 10 seconds - certainly not even close to 30 seconds. 
Just wanted to throw that out there.

Other than that, I believe using the noauto option together with a 
custom systemd service sounds like it should do the trick (and sounds 
like a clean solution if you indeed want that filesystem mounted on 
demand only), but then again, mounting a filesystem without that option 
should work too. In any case, I've saved your email, maybe I'll hit that 
issue again someday - I'll try your suggestion then.


Philip

  reply	other threads:[~2015-07-27 19:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 18:41 systemd : Timed out waiting for defice dev-disk-by… Vincent Olivier
2015-07-24 18:43 ` Vincent Olivier
2015-07-24 19:26 ` Tomasz Torcz
2015-07-24 19:27 ` Chris Murphy
     [not found]   ` <1437766634.808316031@apps.rackspace.com>
2015-07-24 19:49     ` Chris Murphy
2015-07-26 20:39 ` Philip Seeger
2015-07-27  5:20   ` Duncan
2015-07-27 19:16     ` Philip Seeger [this message]
2015-07-30 11:22     ` Rich Freeman
2015-07-31  8:44       ` Duncan
2015-07-31 12:40         ` Philip Seeger
2016-03-25  7:41 ` Qu Wenruo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55B68396.1030505@googlemail.com \
    --to=p0h0i0l0i0p@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox