From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: mkfs.btrfs/balance small-btrfs chunk size RFC
Date: Wed, 11 Jan 2017 19:25:57 +0000 (UTC) [thread overview]
Message-ID: <pan$d5335$4c7aeed6$8086366b$7bb695a1@cox.net> (raw)
In-Reply-To: db8aff8c-44a5-f488-56de-4a9ec87e44e0@gmail.com
Austin S. Hemmelgarn posted on Tue, 10 Jan 2017 09:57:52 -0500 as
excerpted:
> I can't personally comment on the code itself right now (I've actually
> never looked at the mkfs code, or any of the stuff that deals with the
> System chunk), but I can make a few general comments on this:
> 1. This behavior is still the case as of a Git build from yesterday (I
> just verified this myself with the locally built copy of btrfs-progs on
> my laptop).
Thanks. After posting and seeing Qu W's response I was thinking I needed
to test current behavior, and you just saved me the trouble (tho I do
need to freshen my backup /boot one of these days, likely testing
mkfs.btrfs on this in the process, but that can wait until 4.10).
--
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
prev parent reply other threads:[~2017-01-11 19:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 3:55 mkfs.btrfs/balance small-btrfs chunk size RFC Duncan
2017-01-10 5:34 ` Qu Wenruo
2017-01-10 14:57 ` Austin S. Hemmelgarn
2017-01-10 15:29 ` Hugo Mills
2017-01-10 15:42 ` Austin S. Hemmelgarn
2017-01-10 15:47 ` Hugo Mills
2017-01-10 16:05 ` Austin S. Hemmelgarn
2017-01-10 16:10 ` Hugo Mills
2017-01-11 19:00 ` Duncan
2017-01-10 17:17 ` Austin S. Hemmelgarn
2017-01-11 19:25 ` Duncan [this message]
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$d5335$4c7aeed6$8086366b$7bb695a1@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).