linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Duncan <1i5t5.duncan@cox.net>,
	linux-btrfs@vger.kernel.org, covici@ccs.covici.com,
	conicawd@gmail.com
Subject: Re: Btrfs Check - "type mismatch with chunk"
Date: Sun, 27 Dec 2015 05:01:28 +0100	[thread overview]
Message-ID: <1451188888.6446.18.camel@scientia.net> (raw)
In-Reply-To: <pan$ed44$b7377cf0$bc775a24$c5211738@cox.net>

[-- Attachment #1: Type: text/plain, Size: 431 bytes --]

On Thu, 2015-12-24 at 23:41 +0000, Duncan wrote:
> as the patch is in the userspace  4.3.1 you're running.
I don't think this is the case.

The commit was b08a740d7b797d870cbc3691b1291290d0815998 and AFAICT,
it's not included in any release yet.

4.3.1 was from Nov 16th, the above commit was from the 26th.


As I've said before, please try with the patch applied (it's in the
devel branch only).


Cheers,
Chris.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]

  parent reply	other threads:[~2015-12-27  4:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24 19:15 Btrfs Check - "type mismatch with chunk" Zach Fuller
2015-12-24 21:27 ` Christoph Anton Mitterer
2015-12-24 23:41 ` Duncan
2015-12-25  5:28   ` covici
2015-12-25  8:06     ` Duncan
2016-01-02  5:12       ` Christoph Anton Mitterer
2016-01-05 15:34         ` Duncan
2016-01-05 18:54           ` Christoph Anton Mitterer
2016-01-05 19:01           ` Martin Steigerwald
2015-12-27  4:01   ` Christoph Anton Mitterer [this message]
2015-12-29  0:08     ` Zach Fuller
2015-12-29  4:16       ` Duncan
2015-12-29  4:42       ` Christoph Anton Mitterer
2016-01-02 10:48   ` Martin Steigerwald
2016-01-02 19:52     ` Henk Slager

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=1451188888.6446.18.camel@scientia.net \
    --to=calestyo@scientia.net \
    --cc=1i5t5.duncan@cox.net \
    --cc=conicawd@gmail.com \
    --cc=covici@ccs.covici.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).