linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nazar Mokrynskyi <nazar@mokrynskyi.com>
To: Chris Murphy <lists@colorremedies.com>,
	Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Unrecoverable btrfs corruption (backref bytes do not match extent backref)
Date: Sat, 5 Jan 2019 02:13:47 +0200	[thread overview]
Message-ID: <b070d4f5-15e5-ea9d-51d6-795957ec972a@mokrynskyi.com> (raw)
In-Reply-To: <CAJCQCtTJEc8q8hrBG_HRvm1vWQvs5KgcFUKfvXPjxTNZSjd-Sg@mail.gmail.com>

04.01.19 03:15, Chris Murphy пише:
> What do you get with 'btrfs check --mode=lowmem' ? This is a different
> implementation of check, and might reveal some additional information
> useful to developers. It is wickedly slow however.
root@nazarpc-Standard-PC-Q35-ICH9-2009:~# btrfs check --mode=lowmem /dev/vdb
warning, bad space info total_bytes 2155872256 used 2155876352
warning, bad space info total_bytes 3229614080 used 3229618176
warning, bad space info total_bytes 4303355904 used 4303360000
warning, bad space info total_bytes 5377097728 used 5377101824
warning, bad space info total_bytes 6450839552 used 6450843648
warning, bad space info total_bytes 7524581376 used 7524585472
warning, bad space info total_bytes 8598323200 used 8598327296
warning, bad space info total_bytes 9672065024 used 9672069120
warning, bad space info total_bytes 10745806848 used 10745810944
warning, bad space info total_bytes 11819548672 used 11819552768
warning, bad space info total_bytes 12893290496 used 12893294592
warning, bad space info total_bytes 13967032320 used 13967036416
warning, bad space info total_bytes 15040774144 used 15040778240
warning, bad space info total_bytes 16114515968 used 16114520064
warning, bad space info total_bytes 17188257792 used 17188261888
warning, bad space info total_bytes 18261999616 used 18262003712
warning, bad space info total_bytes 19335741440 used 19335745536
warning, bad space info total_bytes 20409483264 used 20409487360
warning, bad space info total_bytes 21483225088 used 21483229184
warning, bad space info total_bytes 22556966912 used 22556971008
warning, bad space info total_bytes 23630708736 used 23630712832
warning, bad space info total_bytes 24704450560 used 24704454656
warning, bad space info total_bytes 25778192384 used 25778196480
warning, bad space info total_bytes 26851934208 used 26851938304
warning, bad space info total_bytes 27925676032 used 27925680128
warning, bad space info total_bytes 28999417856 used 28999421952
warning, bad space info total_bytes 30073159680 used 30073163776
warning, bad space info total_bytes 31146901504 used 31146905600
warning, bad space info total_bytes 32220643328 used 32220647424
Checking filesystem on /dev/vdb
UUID: 5170aca4-061a-4c6c-ab00-bd7fc8ae6030
checking extents
checking free space cache
checking fs roots
ERROR: root 304 INODE REF[274921, 256895] name 25da95e3e893bb2fa69a2f0acd77bfe725626a1e filetype 1 missing
ERROR: root 304 EXTENT_DATA[910393 4096] gap exists, expected: EXTENT_DATA[910393 25]
ERROR: root 304 EXTENT_DATA[910393 8192] gap exists, expected: EXTENT_DATA[910393 4121]
ERROR: root 304 EXTENT_DATA[910393 16384] gap exists, expected: EXTENT_DATA[910393 12313]
ERROR: root 304 EXTENT_DATA[910400 4096] gap exists, expected: EXTENT_DATA[910400 25]
ERROR: root 304 EXTENT_DATA[910400 8192] gap exists, expected: EXTENT_DATA[910400 4121]
ERROR: root 304 EXTENT_DATA[910400 16384] gap exists, expected: EXTENT_DATA[910400 12313]
ERROR: root 304 EXTENT_DATA[910401 4096] gap exists, expected: EXTENT_DATA[910401 25]
ERROR: root 304 EXTENT_DATA[910401 8192] gap exists, expected: EXTENT_DATA[910401 4121]
ERROR: root 304 EXTENT_DATA[910401 16384] gap exists, expected: EXTENT_DATA[910401 12313]
ERROR: root 101721 INODE REF[274921, 256895] name 25da95e3e893bb2fa69a2f0acd77bfe725626a1e filetype 1 missing
ERROR: root 101721 EXTENT_DATA[910393 4096] gap exists, expected: EXTENT_DATA[910393 25]
ERROR: root 101721 EXTENT_DATA[910393 8192] gap exists, expected: EXTENT_DATA[910393 4121]
ERROR: root 101721 EXTENT_DATA[910393 16384] gap exists, expected: EXTENT_DATA[910393 12313]
ERROR: root 101721 EXTENT_DATA[910400 4096] gap exists, expected: EXTENT_DATA[910400 25]
ERROR: root 101721 EXTENT_DATA[910400 8192] gap exists, expected: EXTENT_DATA[910400 4121]
ERROR: root 101721 EXTENT_DATA[910400 16384] gap exists, expected: EXTENT_DATA[910400 12313]
ERROR: root 101721 EXTENT_DATA[910401 4096] gap exists, expected: EXTENT_DATA[910401 25]
ERROR: root 101721 EXTENT_DATA[910401 8192] gap exists, expected: EXTENT_DATA[910401 4121]
ERROR: root 101721 EXTENT_DATA[910401 16384] gap exists, expected: EXTENT_DATA[910401 12313]
ERROR: errors found in fs roots
found 39410126848 bytes used, error(s) found
total csum bytes: 35990412
total tree bytes: 196955471872
total fs tree bytes: 196809785344
total extent tree bytes: 96534528
btree space waste bytes: 33486070155
file data blocks allocated: 1705720172544
 referenced 2238568390656


      parent reply	other threads:[~2019-01-05  0:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 22:06 Unrecoverable btrfs corruption (backref bytes do not match extent backref) Nazar Mokrynskyi
2019-01-04  1:15 ` Chris Murphy
2019-01-04  1:32   ` Qu Wenruo
2019-01-04  1:36     ` Hans van Kranenburg
2019-01-04  3:43     ` Chris Murphy
2019-01-04  4:31       ` Qu Wenruo
2019-01-04 23:04     ` Nazar Mokrynskyi
2019-01-05  1:18       ` Qu Wenruo
2019-01-05  1:26         ` Nazar Mokrynskyi
2019-01-05  0:13   ` Nazar Mokrynskyi [this message]

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=b070d4f5-15e5-ea9d-51d6-795957ec972a@mokrynskyi.com \
    --to=nazar@mokrynskyi.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).