linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@mikefedyk.com>
To: Marek Otahal <markotahal@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs-progs: Update man page for mixed data+metadata option.
Date: Fri, 12 Nov 2010 08:56:02 -0800	[thread overview]
Message-ID: <AANLkTi=F+R55Kp3DzgHPz9BJY7v_fjqQ=yxD5cAsk1aJ@mail.gmail.com> (raw)
In-Reply-To: <201011122228.37322.markotahal@gmail.com>

On Fri, Nov 12, 2010 at 6:28 AM, Marek Otahal <markotahal@gmail.com> wr=
ote:
> On Friday 12 of November 2010 18:44:12 you wrote:
>> On Thu, Nov 11, 2010 at 11:41 PM, Josef Bacik <josef@redhat.com> wro=
te:
>> > 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=
, it 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 f=
or
>> > anything less than 5 GiB, and you're only looking at about a 5-10%=
 perf
>> > degredation when using it on larger filesystems. =C2=A0Thanks,
>>
>> Then a warning of 10% slowdown if > 10GB would be good. =C2=A0It'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...
> My 2c: I'm against bloating the program just because of people who do=
n't RTFM.
> Just mention it clearly in docs and that's enough, linux does what it=
's asked
> for, not the "Are you really really sure you want to do this?" known =
from some
> other OS. Anyway, btrfs-progs would be probably run by a user with ro=
ot

I was thinking of what ssh does when it sees a changed key...
--
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

  reply	other threads:[~2010-11-12 16:56 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
2010-11-12 14:28             ` Marek Otahal
2010-11-12 16:56               ` Mike Fedyk [this message]
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='AANLkTi=F+R55Kp3DzgHPz9BJY7v_fjqQ=yxD5cAsk1aJ@mail.gmail.com' \
    --to=mfedyk@mikefedyk.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=markotahal@gmail.com \
    /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).