From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: About free space fragmentation, metadata write amplification and (no)ssd
Date: Sun, 28 May 2017 03:54:13 +0000 (UTC) [thread overview]
Message-ID: <pan$190df$2ad31a2b$6071471$3fd0fb2c@cox.net> (raw)
In-Reply-To: d5ebd421-52a1-5b91-72a3-f97a2fb9628f@mendix.com
Hans van Kranenburg posted on Sun, 28 May 2017 02:59:57 +0200 as
excerpted:
>> Note that our metadata is still DUP, and it doesn't have skinny extent
>> tree metadata yet. It was originally created with btrfs-progs 3.17, and
>> when we realized we should have single it was too late. I want to
>> change that and see if I can convert on a NetApp clone. This should
>> reduce extent tree metadata size by maybe more than 60% and
>> whoknowswhat will happen to the abhorrent write traffic.
>
> Yeah, blabla... Converting metadata from DUP to single is a big no go
> with btrfs balance, that's what I clearly got figured out now.
Umm... Did you try -f (force)? See the manpage.
OTOH, I'd have thought that was obvious enough you'd have tried it which
would make the problem here something not so simple, but then again, I'd
have thought you'd mention trying it too, if you did, to prevent exactly
this sort of followup. So I don't know what to think, except I think
it's worth covering the possibility just in case.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-05-28 3:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 20:19 About free space fragmentation, metadata write amplification and (no)ssd Hans van Kranenburg
2017-04-08 21:55 ` Peter Grandi
2017-04-09 0:21 ` Hans van Kranenburg
2017-04-09 0:39 ` Hans van Kranenburg
2017-04-09 3:14 ` Kai Krakow
2017-04-09 20:48 ` Hans van Kranenburg
2017-04-09 6:38 ` Paul Jones
2017-04-09 8:43 ` Roman Mamedov
2017-04-09 18:10 ` Chris Murphy
2017-04-09 20:15 ` Hans van Kranenburg
2017-04-10 12:23 ` Austin S. Hemmelgarn
2017-04-10 22:59 ` Hans van Kranenburg
2017-04-11 11:33 ` Austin S. Hemmelgarn
2017-04-11 13:13 ` Kai Krakow
2017-05-28 0:59 ` Hans van Kranenburg
2017-05-28 3:54 ` Duncan [this message]
2017-06-08 17:57 ` Hans van Kranenburg
2017-06-08 18:47 ` Roman Mamedov
2017-06-08 19:19 ` Hans van Kranenburg
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$190df$2ad31a2b$6071471$3fd0fb2c@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).