From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs-progs-3.16: fs metadata is both single and dup?
Date: Tue, 2 Sep 2014 12:34:12 +0000 (UTC) [thread overview]
Message-ID: <pan.2014.09.02.12.34.12@googlemail.com> (raw)
In-Reply-To: 20140902121349.GF18897@carfax.org.uk
On Tue, 02 Sep 2014 13:13:49 +0100, Hugo Mills wrote:
> [snip]
>> So where does the confusing initial display come from? I'm running this
>> against a (very patched) 3.14.17, but don't remember ever seeing this
>> with btrfs-progs-3.14.2.
>
> Your memory is faulty, I'm afraid. It's always done that -- at
After 40 it's all downhill.. :-)
> least since I started using btrfs, several years ago.
Alright then. I was just getting nervous I might have borked something
either with my kernel or that the new progs somehow get information from
the kernel that is off/wrong.
All my other filesystems display as expected, but they have been balanced
previously - so nothing to see there.
Thanks!
Holger
next prev parent reply other threads:[~2014-09-02 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 12:05 Btrfs-progs-3.16: fs metadata is both single and dup? Holger Hoffstätte
2014-09-02 12:13 ` Hugo Mills
2014-09-02 12:34 ` Holger Hoffstätte [this message]
2014-09-03 4:53 ` Duncan
2014-09-03 7:33 ` Hugo Mills
2014-09-03 8:41 ` Duncan
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.02.12.34.12@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).