From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: device delete progress
Date: Mon, 22 Sep 2014 16:29:26 +0000 (UTC) [thread overview]
Message-ID: <pan$c3643$3e5c01cf$cc7cb117$c2a00b4b@cox.net> (raw)
In-Reply-To: 20140922094955.GI9715@twin.jikos.cz
David Sterba posted on Mon, 22 Sep 2014 11:49:55 +0200 as excerpted:
> The upcomming 3.17 release should contain all the 'new df' patches that
> were unfortunatelly delayed. There are some minor issues to be fixed but
> I hope it'll be ready close to the kernel 3.17 release.
Will that fix my "unknown" chunk profiles too?
I expected either userspace 3.16 or kernel 3.17 to fix that, but I'm
running both (well, kernel 3.17 git, since the release hasn't happened
yet) and still seeing the unknown chunk profiles.
Either that, or if userspace 3.16 and kernel 3.17 should have fixed it,
I'm triggering a bug somewhere.
--
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:[~2014-09-22 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 2:09 device delete progress Russell Coker
2014-09-21 8:34 ` Duncan
2014-09-22 9:49 ` David Sterba
2014-09-22 16:29 ` Duncan [this message]
2014-09-22 19:23 ` Duncan
2014-09-21 17:12 ` Chris Murphy
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$c3643$3e5c01cf$cc7cb117$c2a00b4b@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).