All of lore.kernel.org
 help / color / mirror / Atom feed
From: cwillu <cwillu@cwillu.com>
To: Marguerite Su <i@marguerite.su>
Cc: Chris Mason <chris.mason@fusionio.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: initramfs take a long time to load[135s]
Date: Fri, 19 Oct 2012 14:56:55 -0600	[thread overview]
Message-ID: <CAE5mzviDoqnNmeZyeM_TP26x0um3wfFx06pUm0ww0Dw+YB2rYA@mail.gmail.com> (raw)
In-Reply-To: <CAK0PdA=RqD7rAywEkU_fpRjAm58HX1WbGwK8Pfx6CXZJ2e8pEQ@mail.gmail.com>

On Fri, Oct 19, 2012 at 1:02 PM, Marguerite Su <i@marguerite.su> wrote:
> On Sat, Oct 20, 2012 at 2:35 AM, cwillu <cwillu@cwillu.com> wrote:
>> Without space_cache (once), btrfs has to repopulate that information
>> the slow way every mount; with it, it can just load the data from the
>> last unmount (modulo some consistency checks).
>>
>> The setting is sticky, so you don't actually need it in fstab any more
>> (although it won't hurt anything either).
>
> Thanks, cwillu!
>
> I transfer the message to openSUSE bugzilla and ask them help making
> that happen by default in openSUSE.
>
> Marguerite

Apparently mkfs.btrfs does set it by default now, so perhaps your
filesystem predates the change, or suse's btrfs-progs is too old.

mkfs.btrfs /dev/whatever followed by mounting with no options should
print "btrfs: disk space caching is enabled" to dmesg if your mkfs is
new enough, if you wish to test.

  reply	other threads:[~2012-10-19 20:56 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
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 [this message]
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=CAE5mzviDoqnNmeZyeM_TP26x0um3wfFx06pUm0ww0Dw+YB2rYA@mail.gmail.com \
    --to=cwillu@cwillu.com \
    --cc=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.