linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Wiki bug re. metadata_ratio mount option
Date: Sat, 27 Sep 2014 16:23:19 +0000 (UTC)	[thread overview]
Message-ID: <pan.2014.09.27.16.23.19@googlemail.com> (raw)


The wiki page https://btrfs.wiki.kernel.org/index.php/Mount_options has
outdated information regarding the "metadata-ratio" option.

It says:

 metadata_ratio=number
   Sets the number of data chunks that need to be allocated to force a
   metadata chunk allocation. By default this is set to 8 (meaning that
   data:metadata are 1:8). 

Both the 'mount' man page and a look at the code (disk-io.c:open_ctree())
confirm that this is incorrect, and that forced metadata chunk allocation
will be skipped by default.

Could someone with an account please update this?

Thanks,
Holger


                 reply	other threads:[~2014-09-27 16:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.2014.09.27.16.23.19@googlemail.com \
    --to=holger.hoffstaette@googlemail.com \
    --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 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).