From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs mount flags
Date: Mon, 16 Apr 2012 03:20:53 +0000 (UTC) [thread overview]
Message-ID: <pan.2012.04.16.03.20.53@cox.net> (raw)
In-Reply-To: 201204151200.31568.Martin@lichtvoll.de
Martin Steigerwald posted on Sun, 15 Apr 2012 12:00:31 +0200 as excerpted:
> No cc - instead of whats habit on this list - as you prefer list
> replies.
>
> Am Sonntag, 15. April 2012 schrieb Duncan:
>> I believe there's a current report of a performance regression due to
>> the space cache [but] the expectation is a fix by 3.4 release[.]
>> [A]t least people with existing btrfs filesystems might
>> want to hold off on enabling that option for the moment, if they're
>> running the 3.4-rcs, but by 3.4 release, it'll hopefully be fine.
>
> Maybe a fix will be in some rc candidate before 3.4 release.
I just did a git-pull and see the commit fixing the space-cache bug made
it for 3.4-rc3. So the space-cache mount option should be good to go,
now. Of course btrfs being a development/experimental filesystem,
there's other bugs in process, but that's normal state for current
maturity. This one's fixed, anyway.
> Maybe an update wiki page could serve as input for additions to mount
> Manpage. Or a special btrfs mount options manpage. I would be willing to
> help with that as time permits.
Both would probably be useful.
The mount (8) manpage isn't likely to be reliably current on btrfs for
some time, as btrfs is simply developing too rapidly at this point for
the general-purpose mount docs to keep up. So btrfs-tools shipping a
mount.btrfs manpage or whatever could be quite useful if it's kept
updated, of course the nice thing about manpages being that they're
generally usable without a net connection.
But the wiki page with the mount options should be kept updated as well.
Since it's there already and simply needs upkeep, that'd be the cheaper
alternative for the moment, and an online reference for people to read if
they don't have btrfs-tools installed locally is as useful as a local
manpage reference for those with it local but no net. =:^)
As for updating the wiki... I really should get a login for it so I
can... (I didn't see the usual edit links when not logged in. Not that
I blame whoever's running it. This isn't wikipedia and keeping up with
the spam, etc, would be a serious problem if registration wasn't
required.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2012-04-16 3:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 15:50 btrfs mount flags Kai Krakow
2012-04-13 17:42 ` Duncan
2012-04-14 15:17 ` Kai Krakow
2012-04-15 5:53 ` Duncan
2012-04-15 10:00 ` Martin Steigerwald
2012-04-16 3:20 ` Duncan [this message]
2012-04-13 22:05 ` Martin Steigerwald
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=pan.2012.04.16.03.20.53@cox.net \
--to=1i5t5.duncan@cox.net \
--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.