From: Hans van Kranenburg <Hans.van.Kranenburg@mendix.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Chris Murphy <lists@colorremedies.com>,
Nazar Mokrynskyi <nazar@mokrynskyi.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Unrecoverable btrfs corruption (backref bytes do not match extent backref)
Date: Fri, 4 Jan 2019 01:36:48 +0000 [thread overview]
Message-ID: <e0422250-b985-668f-e6a9-909cbbbe56f9@mendix.com> (raw)
In-Reply-To: <aca3ce08-2cc6-9ace-ec3f-a9d963b4dab8@gmx.com>
On 1/4/19 2:32 AM, Qu Wenruo wrote:
>
>
> On 2019/1/4 上午9:15, Chris Murphy wrote:
>> On Thu, Jan 3, 2019 at 3:13 PM Nazar Mokrynskyi <nazar@mokrynskyi.com> wrote:
>>
>>> root@ubuntu:~# btrfsck /dev/mapper/luks-739967f1-9770-470a-a031-8d8b8bcdb350
>>> 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
>
> I'm not sure what this means.
> I thought it's free space cache, but code doesn't prove that.
I was thinking about a 'space', which in btrfs, is a collection of all
block groups which have a specific combination of type/profile, like
'Data, RAID1'.
Note that the difference between the two numbers in every line seems to
be 4096 bytes.
> [...]
--
Hans van Kranenburg
next prev parent reply other threads:[~2019-01-04 1:36 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 [this message]
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
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=e0422250-b985-668f-e6a9-909cbbbe56f9@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=nazar@mokrynskyi.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