All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Scrub CPU usage ...
Date: Sun, 05 May 2013 03:21:22 +0200	[thread overview]
Message-ID: <dpog5a-t12.ln1@hurikhan.ath.cx> (raw)
In-Reply-To: 518555FF.4020704@chinilu.com

George Mitchell <george@chinilu.com> schrieb:

> 1)  The system fails to boot intermittently due to dracut/initrd issues
> (btrfs: open_ctree failed).  This is being worked on upstream and I am
> seeing a continual flow of patches addressing it, but so far no fix.
> This will take time to fix and it usually leaps to life in 3 attempts or
> less.

Try rootdelay=1 or a higher number. This solved exactly that problem for me. 
It will delay mounting the rootfs by the given number of seconds. You need 
to pass this on the kernel command line, probably using grub. This seems to 
only be needed with multi-device btrfs as rootfs.

Greetings,
Kai


  reply	other threads:[~2013-05-05  1:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-04 18:39 Scrub CPU usage George Mitchell
2013-05-05  1:21 ` Kai Krakow [this message]
2013-05-05  1:58   ` George Mitchell
2013-05-05  9:22 ` Martin Steigerwald
2013-05-05 14:15   ` George Mitchell

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=dpog5a-t12.ln1@hurikhan.ath.cx \
    --to=hurikhan77+btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.