From: Mike Fedyk <mfedyk@mikefedyk.com>
To: Josef Bacik <josef@redhat.com>
Cc: Chris Samuel <chris@csamuel.org>,
Mitch Harder <mitch.harder@sabayonlinux.org>,
linux-btrfs@vger.kernel.org
Subject: Re: Btrfs-progs: Update man page for mixed data+metadata option.
Date: Fri, 12 Nov 2010 02:44:12 -0800 [thread overview]
Message-ID: <AANLkTikvR_1Jpz6unuuGDWSB0eUoNMFMeL-zUQyw1FOz@mail.gmail.com> (raw)
In-Reply-To: <20101112074105.GD10179@dhcp231-156.rdu.redhat.com>
On Thu, Nov 11, 2010 at 11:41 PM, Josef Bacik <josef@redhat.com> wrote:
> On Fri, Nov 12, 2010 at 05:47:14PM +1100, Chris Samuel wrote:
>> On 11/11/10 23:52, Josef Bacik wrote:
>>
>> > This feature incurs a performance penalty in larger filesystems, i=
t is
>> > recommended for use with filesystems of 1 GiB or smaller.
>>
>> Maybe slightly stronger, for example:
>>
>> This feature incurs a performance penalty for larger filesystems and=
it
>> is ONLY recommended for use with filesystems of 1 GiB or smaller.
>>
>> Is it worth having a check and a warning printed if a user does
>> try and make a filesystem larger than 1GiB with this option ?
>>
>> Just in case they don't RTFM...
>>
>
> No because depending on your usage it's actually kind of usefull for =
anything
> less than 5 GiB, and you're only looking at about a 5-10% perf degred=
ation when
> using it on larger filesystems. =C2=A0Thanks,
>
Then a warning of 10% slowdown if > 10GB would be good. It's
surprising how many will just read some forum post and not concern
themselves with the docs at all.
And making them type "yes" if > 100GB is probably a good idea too...
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-12 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 18:02 Btrfs-progs: Update man page for mixed data+metadata option Mitch Harder
2010-11-11 2:10 ` Josef Bacik
2010-11-11 3:53 ` Mitch Harder
2010-11-11 3:59 ` C Anthony Risinger
2010-11-11 12:52 ` Josef Bacik
2010-11-12 6:47 ` Chris Samuel
2010-11-12 7:41 ` Josef Bacik
2010-11-12 10:44 ` Mike Fedyk [this message]
2010-11-12 14:28 ` Marek Otahal
2010-11-12 16:56 ` Mike Fedyk
2010-11-15 16:28 ` Mitch Harder
2010-11-12 15:59 ` Mitch Harder
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=AANLkTikvR_1Jpz6unuuGDWSB0eUoNMFMeL-zUQyw1FOz@mail.gmail.com \
--to=mfedyk@mikefedyk.com \
--cc=chris@csamuel.org \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).