From: Andreas Schwab <schwab@linux-m68k.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Qu Wenruo <wqu@suse.com>,
u-boot@lists.denx.de, linux-btrfs@vger.kernel.org,
Sam Winchenbach <swichenbach@tethers.com>
Subject: Re: [PATCH] fs/btrfs: handle data extents, which crosss stripe boundaries, correctly
Date: Mon, 13 Feb 2023 19:25:33 +0100 [thread overview]
Message-ID: <87ttzpjuci.fsf@igel.home> (raw)
In-Reply-To: <8a85a4bc-3791-72ed-fe9b-b08a36b2ee21@gmx.com> (Qu Wenruo's message of "Mon, 13 Feb 2023 08:19:51 +0800")
On Feb 13 2023, Qu Wenruo wrote:
> On 2023/2/13 00:20, Andreas Schwab wrote:
>> When I print ce->size in __btrfs_map_block, it is almost always
>> 1073741824, which looks bogus.
>>
> Can you provide the image of that filesystem?
How do I do that?
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2023-02-13 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 1:07 [PATCH] fs/btrfs: handle data extents, which crosss stripe boundaries, correctly Qu Wenruo
2023-01-12 15:19 ` Tom Rini
2023-02-12 15:37 ` Andreas Schwab
2023-02-12 16:01 ` Andreas Schwab
2023-02-12 16:20 ` Andreas Schwab
2023-02-13 0:19 ` Qu Wenruo
2023-02-13 18:25 ` Andreas Schwab [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=87ttzpjuci.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=swichenbach@tethers.com \
--cc=u-boot@lists.denx.de \
--cc=wqu@suse.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