From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs fi df "unknown"
Date: Mon, 21 Apr 2014 23:00:34 +0000 (UTC) [thread overview]
Message-ID: <pan$6e106$ce6c8992$24f8fddd$735743cb@cox.net> (raw)
In-Reply-To: 535511FE.8070608@fb.com
Chris Mason posted on Mon, 21 Apr 2014 08:41:34 -0400 as excerpted:
> 3.15 has this commit, it's the cause of the unknown.
[Since I already replied to thread.]
That would explain why I haven't seen it yet. I'm still running kernel
3.14 as I'm trying to catch up on some other stuff before I upgrade to
3.15-rc. Tho I try to upgrade before rc4 at the latest, so if I spot any
bugs I can report 'em with some time to fix before release. Which gives
me a week or so...
--
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:[~2014-04-21 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 20:18 btrfs fi df "unknown" Chris Murphy
2014-04-20 20:26 ` btrfs fi df "unknown" chunk type Chris Murphy
2014-04-21 6:54 ` Duncan
2014-04-21 12:41 ` btrfs fi df "unknown" Chris Mason
2014-04-21 23:00 ` 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$6e106$ce6c8992$24f8fddd$735743cb@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).