linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Freyermuth <o.freyermuth@googlemail.com>
To: linux-btrfs@vger.kernel.org
Cc: Oliver Freyermuth <o.freyermuth@googlemail.com>
Subject: Re: btrfstune settings
Date: Sun, 28 Aug 2016 18:18:52 +0200	[thread overview]
Message-ID: <df5ff0e5-f07b-72ca-f49f-e9cf2e2c6e39@googlemail.com> (raw)
In-Reply-To: <pan$852e9$bd44e66c$65d119d9$c6922137@cox.net>

(sorry if my Message-ID header is missing, I am not subscribed to the mailing list, 
so I reply using mail-archive)

> Try btrfs-show-super <device>.  The incompat_flags section enumerates the 
> flags that are on (at least with a reasonably new btrfs-progs).

Thanks a lot for this hint - I totally missed that, since I only looked 
at manpages and features of the "all-in-one" btrfs tool up to now. 
Also thanks for the hint to /sys/fs/btrfs, this is even more readable! 

And thanks a lot for your detailed answer(s) in general! 

> In general it should be safe to activate flags via btrfstune, but since 
> they'll generally apply only to newly written data, any benefits on a 
> mature filesystem will be limited.  For that reason as well as to get the 
> benefit of 16K nodesize which you can't except at creation, I recommend 
> backing up and recreating the filesystem from a fresh mkfs.btrfs.

That would certainly be the best option, however, 
I have two issues with that: 
- Any replay of a backup will do a lot of writes on the SSD, 
  reducing lifetime. 
- I did not yet figure out a working way to get a "complete" backup for a btrfs. 
  btrfs send is too slow for me, and rsync does an incomplete backup, 
  since all FS-special attrs (like the NOCOW attr from 'chattr +C')
  are not copied, even when xattr copy is on. 

My last backup replay was from an rsync backup (these I do regularly) 
and afterwards I did a manual fixing of these special attrs, which is some bit of extra work. 
Also, the machine is offline during backup replay, 
while I could still use it during a simple rebalance. 

The good news is my old FS already has 16K leafsize, it's only missing skinny metadata
(and no-holes, apparently that's not default in mkfs.btrfs yet?). 

This reduces the scope of my question a bit - is it sufficient and worthwhile to "btrfstune -x" 
and then "btrfs balance start -musage=0 /" to convert all metadata, and thus gain some space? 

Or are the gains not worth it and I should just wait until the next time I need to replay a backup for other reasons? 

Cheers and thanks for your reply, 
	Oliver

  parent reply	other threads:[~2016-08-28 16:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28  3:42 btrfstune settings Oliver Freyermuth
2016-08-28  8:27 ` Duncan
2016-08-28 13:30   ` Kai Krakow
2016-08-28 16:18   ` Oliver Freyermuth [this message]
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=df5ff0e5-f07b-72ca-f49f-e9cf2e2c6e39@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 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).