All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Krig <robert.krig@render-wahnsinn.de>
To: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS Raid5 error during Scrub.
Date: Thu, 03 Oct 2019 14:18:32 +0200	[thread overview]
Message-ID: <498f23ebd3889618cb3faedf04c72ff059553121.camel@render-wahnsinn.de> (raw)
In-Reply-To: <273d41c4d05283aaa658d9c374e7c43199b0aac3.camel@render-wahnsinn.de>

By the way, how serious is the error I've encountered?
I've run a second scrub in the meantime, it aborted when it came close
to the end, just like the first time. 
If the files that are corrupt have been deleted is this error going to
go away?



On Mi, 2019-10-02 at 12:17 +0200, Robert Krig wrote:
> Here's the output of btrfs insp dump-t -b 48781340082176 /dev/sda
> 
> Since /dev/sda is just one device from my RAID5, I'm guessing the
> command doesn't need to be run separately for each device member of
> my
> BTRFS Raid5 setup.
> 
> http://paste.debian.net/1103596/
> 
> 
> Am Dienstag, den 01.10.2019, 12:10 -0600 schrieb Chris Murphy:
> > On Mon, Sep 30, 2019 at 3:37 AM Robert Krig
> > <robert.krig@render-wahnsinn.de> wrote:
> > > I've upgraded to btrfs-progs v5.2.1
> > > Here is the output from btrfs check -p --readonly /dev/sda
> > > 
> > > 
> > > Opening filesystem to check...
> > > Checking filesystem on /dev/sda
> > > UUID: f7573191-664f-4540-a830-71ad654d9301
> > > [1/7] checking root items                      (0:01:17 elapsed,
> > > 5138533 items checked)
> > > parent transid verify failed on 48781340082176 wanted 109181
> > > found
> > > 109008items checked)
> > > parent transid verify failed on 48781340082176 wanted 109181
> > > found
> > > 109008
> > > parent transid verify failed on 48781340082176 wanted 109181
> > > found
> > > 109008
> > > Ignoring transid failure
> > > leaf parent key incorrect 48781340082176
> > > bad block 48781340082176
> > > [2/7] checking extents                         (0:03:22 elapsed,
> > > 1143429 items checked)
> > > ERROR: errors found in extent allocation tree or chunk allocation
> > > [3/7] checking free space cache                (0:05:10 elapsed,
> > > 7236
> > > items checked)
> > > parent transid verify failed on 48781340082176 wanted 109181
> > > found
> > > 109008ems checked)
> > > Ignoring transid failure
> > > root 15197 inode 81781 errors 1000, some csum missing48 elapsed,
> > > 33952
> > > items checked)
> > > [4/7] checking fs roots                        (0:42:53 elapsed,
> > > 34145
> > > items checked)
> > > ERROR: errors found in fs roots
> > > found 22975533985792 bytes used, error(s) found
> > > total csum bytes: 16806711120
> > > total tree bytes: 18733842432
> > > total fs tree bytes: 130121728
> > > total extent tree bytes: 466305024
> > > btree space waste bytes: 1100711497
> > > file data blocks allocated: 3891333279744
> > >  referenced 1669470507008
> > 
> > What do you get for
> > # btrfs insp dump-t -b 48781340082176 /dev/
> > 
> > It's possible there will be filenames, it's OK to sanitize them by
> > just deleting the names from the output before posting it.
> > 
> > 
> > 


  reply	other threads:[~2019-10-03 12:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-29 21:38 BTRFS Raid5 error during Scrub Robert Krig
2019-09-30  6:01 ` Nikolay Borisov
2019-09-30  9:37   ` Robert Krig
2019-10-01 18:10     ` Chris Murphy
2019-10-02 10:17       ` Robert Krig
2019-10-03 12:18         ` Robert Krig [this message]
2019-10-03 20:18           ` Chris Murphy
2019-10-04 10:00             ` Robert Krig
2019-09-30  9:56 ` [BTRFS " Graham Cobb

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=498f23ebd3889618cb3faedf04c72ff059553121.camel@render-wahnsinn.de \
    --to=robert.krig@render-wahnsinn.de \
    --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 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.