linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Sindzinski <stesind@gmail.com>
To: Chris Murphy <lists@colorremedies.com>, quwenruo.btrfs@gmx.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: uncorrectable errors in Raid 10
Date: Thu, 23 Nov 2017 13:02:31 +0100	[thread overview]
Message-ID: <63eff0dd-050c-95e5-0bc8-6c151900261c@gmail.com> (raw)
In-Reply-To: <CAJCQCtQKOVYtOmQeCR0GZ08Wew2TjtZzfoA_mDvsHwL5vt06XA@mail.gmail.com>

Hi,

I updated to btrfs-progs v4.14-5-gf09e98a3. Unfortunately after 10h 
Gnome desktop / Arch crashed with btrfs check --lowmem unfinished. I 
will run it this night again.

The result until crash was:

Checking filesystem on /dev/sdd2
UUID: 4fafd0d4-7dd9-4dcc-9a33-5f1ad9555358
ERROR: extent[15923092037632, 73728] referencer count mismatch (root: 
260, owner: 3631467, offset: 1019904) wanted: 4, have: 6
ERROR: extent[16078964924416, 69632] referencer count mismatch (root: 
260, owner: 4086589, offset: 4296704) wanted: 5, have: 7

Steffen


Am 22.11.2017 um 17:42 schrieb Chris Murphy:
> On Wed, Nov 22, 2017 at 9:38 AM, Steffen Sindzinski <stesind@gmail.com> wrote:
>> Hello,
>>
>> I did btrfs check --readonly on both disk without finding any error. To
>> reconfirm I did a scrub again which still has found 2 uncorrectable errors.
> 
> Try --mode=lowmem option with btrfs-progs 4.3.3 or better 4.14. This
> is a new implementation of btrfs check and sometimes it comes up with
> different results. It's strange that there's only this error found by
> scrub and not by btrfs check which should be fully checking all
> metadata for sanity, and in the process it would surely hit a bad
> checksum.
> 
> 

  reply	other threads:[~2017-11-23 12:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-19 19:31 uncorrectable errors in Raid 10 Steffen Sindzinski
2017-11-20  2:03 ` Chris Murphy
2017-11-20 19:28   ` Roy Sigurd Karlsbakk
     [not found]   ` <1c612777-77eb-1b83-101b-a9e0a53ee8be@gmail.com>
     [not found]     ` <CAJCQCtRwO5E_xN-7u22uBQ57sYpUf8qQ7O0Abz2m+K8e9+DgdA@mail.gmail.com>
     [not found]       ` <384b4a21-e74f-c52e-c6e2-f7930f187c94@gmail.com>
2017-11-22 16:42         ` Chris Murphy
2017-11-23 12:02           ` Steffen Sindzinski [this message]
2017-11-23 12:14             ` Qu Wenruo
2017-11-23 14:05               ` Steffen Sindzinski
2017-11-23  0:41         ` Qu Wenruo
  -- strict thread matches above, loose matches on Subject: below --
2017-11-19 16:21 Steffen Sindzinski

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=63eff0dd-050c-95e5-0bc8-6c151900261c@gmail.com \
    --to=stesind@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=quwenruo.btrfs@gmx.com \
    /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).