All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Mitchell <george@chinilu.com>
To: linux-btrfs@vger.kernel.org
Subject: Possible solution to the "open_ctree" boot bug ...
Date: Sun, 02 Jun 2013 07:45:10 -0700	[thread overview]
Message-ID: <51AB5A76.9060203@chinilu.com> (raw)

I am seeing a huge improvement in boot performance since doing a system 
wide file by file defragementation of metadata.  In fact in the four 
sequential boots since completing this process, I have not seen one 
open_ctree failure so far.  This leads me to suspect that the open_ctree 
boot failures that have been plaguing me since install have been related 
to metadata fragmentation.  So I would advise anyone else experiencing 
open_ctree boot problems to defragment their metatdata and see if that 
helps.  It certainly seems to have helped me in that regard.

             reply	other threads:[~2013-06-02 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-02 14:45 George Mitchell [this message]
2013-06-06 20:58 ` Possible solution to the "open_ctree" boot bug Kai Krakow
2013-06-06 23:48   ` George Mitchell
     [not found]     ` <CAMthOuPif30y4JPrNGhnUteajkck65FjwTss0vVFvCs7EM+gvQ@mail.gmail.com>
2013-06-09 13:40       ` George Mitchell
2013-06-11  0:56       ` 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=51AB5A76.9060203@chinilu.com \
    --to=george@chinilu.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.