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
Subject: Re: Btrfs Check - "type mismatch with chunk"
Date: Tue, 05 Jan 2016 19:54:57 +0100	[thread overview]
Message-ID: <1452020097.5722.16.camel@scientia.net> (raw)
In-Reply-To: <pan$2c260$62827c72$5fe5d34$36d9b844@cox.net>

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

On Tue, 2016-01-05 at 15:34 +0000, Duncan wrote:
> >What exactly was that bug in 4.1.1 mkfs and how would one notice
> > that
> > one suffers from it?
> > I created a number of personal filesystems that I use
> > "productively" and
> > I'm not 100% sure during which version I've created them... :/
> > 
> > Is there some easy way to find out, like a fs creation time stamp??
> 
> I believe a current btrfs check will flag the errors, but can't fix
> them, 
> as the problem was in the filesystem creation and is simply too deep
> to 
> fix, so the bad filesystems must be wiped and recreated with a
> mkfs.btrfs 
> without the bug, to fix.
If I didn't mix things up, there was a post by someone just few days
ago, which showed the error that would pop up on fsck.


> the 
> people volunteering (directly or indirectly) to do that coding
> scratch, 
> or choose not to scratch by spending their time and/or resources 
> elsewhere, their own itches in the priority they choose.
Sure that,'s all clear.
And obviously I didn't want to distract anyone from working on it. It's
just if those people wouldn't care on which part of btrfs they're
working,... than I'd have considered btrfs-convert rather just a nice-
to have.


> It's the same reason that I as a kde user who finds the gnome "dumb-
> down" 
> approach horribly frustrating, remain extremely glad there's a gnome 
> project for those who approve of that sort of approach to work on -- 
I'd rather have wished that all those guys get hired by Apple or MS ;-)


Cheers,
Chris.

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

  reply	other threads:[~2016-01-05 18:55 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 [this message]
2016-01-05 19:01           ` Martin Steigerwald
2015-12-27  4:01   ` Christoph Anton Mitterer
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=1452020097.5722.16.camel@scientia.net \
    --to=calestyo@scientia.net \
    --cc=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).