From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Paul Jones <paul@pauljones.id.au>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: gazillions of Incorrect local/global backref count
Date: Sun, 04 Sep 2016 08:33:24 +0200 [thread overview]
Message-ID: <1472970804.11416.3.camel@scientia.net> (raw)
In-Reply-To: <SY3PR01MB138680D8161F8D2B951F65709EE70@SY3PR01MB1386.ausprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On Sun, 2016-09-04 at 05:33 +0000, Paul Jones wrote:
> The errors are wrong. I nearly ruined my filesystem a few days ago by
> trying to repair similar errors, thankfully all seems ok.
> Check again with btrfs-progs 4.6.1 and see if the errors go away,
> mine did.
> See open bug https://bugzilla.kernel.org/show_bug.cgi?id=155791 for
> more details.
Thanks for the pointer :)
I can at least confirm that my system seems to work normal, scrub
didn't bring any errors either, nor are there any kernel messages...
The interesting thing... I have some pretty large btrfs on those 8TiB
seagate disks (nearly full with some million files)... which I have
also scanned with v4.7... and no errors.
Only my system fs seems to be "affected".
Well it's not my first case of false positives in btrfs check (https://
www.mail-archive.com/linux-btrfs@vger.kernel.org/msg48325.html)... so I
was more relaxed this time (at least a bit ;-) ).
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next prev parent reply other threads:[~2016-09-04 6:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 4:50 gazillions of Incorrect local/global backref count Christoph Anton Mitterer
2016-09-04 5:33 ` Paul Jones
2016-09-04 6:33 ` Christoph Anton Mitterer [this message]
2016-09-04 22:41 ` Chris Murphy
2016-09-05 7:27 ` David Sterba
2016-09-05 14:33 ` Christoph Anton Mitterer
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=1472970804.11416.3.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=paul@pauljones.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.