From: Chris Mason <chris.mason@fusionio.com>
To: Marguerite Su <i@marguerite.su>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: initramfs take a long time to load[135s]
Date: Thu, 18 Oct 2012 09:28:50 -0400 [thread overview]
Message-ID: <20121018132850.GA22010@shiny> (raw)
In-Reply-To: <CAK0PdAk3+wPR_MerCNFgCvCC01c1RJ31=Z=G9=hT5eyYfn=iNg@mail.gmail.com>
On Thu, Oct 18, 2012 at 05:29:50AM -0600, Marguerite Su wrote:
> Hi, all,
>
> I ran into a situation that no useful information can be found over
> the internet...
>
> I'm using 3.6.2 + btrfs git compiled using dkms, and I have a 300GB
> btrfs /home and 50GB btrfs /:
Usually when btrfs is slow to mount, or slow right after a mount it is
because we're regenerating the free space cache. This is slow enough
that you should be able to see the free space cache threads active even
after the initial boot is done.
The good news is that you should be able to just let them finish
generating the cache and then the problem should go away.
If it isn't the free space cache, it'll be a fragmentation problem. The
easiest way to tell the difference is to get a few sysrq-w snapshots
during the boot.
-chris
next prev parent reply other threads:[~2012-10-18 13:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 11:29 initramfs take a long time to load[135s] Marguerite Su
2012-10-18 13:28 ` Chris Mason [this message]
2012-10-18 13:58 ` Marguerite Su
2012-10-19 15:28 ` Marguerite Su
2012-10-19 15:41 ` cwillu
2012-10-19 15:53 ` Marguerite Su
2012-10-19 16:18 ` Marguerite Su
2012-10-19 16:29 ` cwillu
2012-10-19 16:55 ` cwillu
2012-10-19 17:02 ` Marguerite Su
2012-10-19 18:26 ` cwillu
2012-10-19 18:33 ` Marguerite Su
2012-10-19 18:35 ` cwillu
2012-10-19 19:02 ` Marguerite Su
2012-10-19 20:56 ` cwillu
2012-10-19 18:29 ` Marguerite Su
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=20121018132850.GA22010@shiny \
--to=chris.mason@fusionio.com \
--cc=i@marguerite.su \
--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.