From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Christian Zangl <coralllama@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: "missing data block" when converting ext4 to btrfs
Date: Mon, 20 Jul 2020 20:56:08 +0800 [thread overview]
Message-ID: <acbe2fee-1462-7631-22cc-19af58da8b57@gmx.com> (raw)
In-Reply-To: <8678a4f9-3388-5a7b-00cc-8b9da6a0a6e8@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 335 bytes --]
Hi Christian,
Thanks for your detailed report.
Now we have pinned down the bug, it's a bit overflow for multiplying
unsigned int.
At least not some fundamental design defeat of btrfs-convert.
The fix has been Cced to you, and passed my local test.
Test case has also been submitted.
Thanks again for your help!
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-20 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 19:46 "missing data block" when converting ext4 to btrfs Christian Zangl
2020-07-14 6:10 ` Qu Wenruo
2020-07-14 7:58 ` Christian Zangl
2020-07-14 8:09 ` Qu Wenruo
2020-07-14 9:33 ` Christian Zangl
2020-07-14 10:10 ` Qu Wenruo
2020-07-15 7:22 ` Christian Zangl
2020-07-20 12:56 ` Qu Wenruo [this message]
2020-07-20 19:33 ` Christian Zangl
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=acbe2fee-1462-7631-22cc-19af58da8b57@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=coralllama@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox