All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Freyermuth <o.freyermuth@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfstune settings
Date: Sun, 28 Aug 2016 05:42:39 +0200	[thread overview]
Message-ID: <fac36170-075c-db45-5aff-afa55bcd9e34@googlemail.com> (raw)

Dear btrfs experts, 

I hope this is the correct place to ask, the wiki and manpages did not help me on these questions. 

BTRFS has gained extended inode refs, skinny metadata and no-holes quite a while ago and these are now the defaults for new mkfs.btrfs. btrfstune can activate those features. 

However, I miss two things: 
- How do I see on an existing FS which of these features are on? 
  btrfstune (it seems) can only "set", but not "get" the feature flags. 
- Is it worthwhile / recommended / safe to activate those on existing FS? 
  Are there any steps (e.g. balancing metadata with -musage=0, I'd guess) needed to make them become active afterwards? 

If there is any documentation on this and I missed it, please RTFM me. 

Cheers and thanks a lot, 
	Oliver

             reply	other threads:[~2016-08-28  3:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28  3:42 Oliver Freyermuth [this message]
2016-08-28  8:27 ` btrfstune settings Duncan
2016-08-28 13:30   ` Kai Krakow
2016-08-28 16:18   ` Oliver Freyermuth
2016-08-28 17:35     ` Kai Krakow
2016-08-28 18:10       ` Oliver Freyermuth
2016-08-28 18:34         ` Lionel Bouton
2016-08-28 19:06         ` Kai Krakow
2016-08-28 17:41     ` Kai Krakow
2016-09-01 17:14 ` David Sterba
2016-09-01 23:54   ` Oliver Freyermuth

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=fac36170-075c-db45-5aff-afa55bcd9e34@googlemail.com \
    --to=o.freyermuth@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 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.