From: Yordan <y16267966@gmail.com>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/3] btrfs-progs: convert: rework file extent iteration to handle unwritten extents
Date: Tue, 7 May 2024 10:48:13 +0300 [thread overview]
Message-ID: <CAE0VrX+tqJ3t3Hmu5wE9fCk2RvgNvEE7UpFs2UVVo02-Zd7+rw@mail.gmail.com> (raw)
In-Reply-To: <bc92cbbcf4c530b18b27a4989767188ba8ea4f96.1715051693.git.wqu@suse.com>
Converted both, the small and the big 24G, images properly - no failed
file checksums anymore.
Thanks, Yordan.
next prev parent reply other threads:[~2024-05-07 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 3:22 [PATCH 0/3] btrfs-progs: convert: proper ext4 unwritten extents handling Qu Wenruo
2024-05-07 3:22 ` [PATCH 1/3] Revert "btrfs-progs: convert: add raid-stripe-tree to allowed features" Qu Wenruo
2024-05-07 3:22 ` [PATCH 2/3] btrfs-progs: convert: rework file extent iteration to handle unwritten extents Qu Wenruo
2024-05-07 7:48 ` Yordan [this message]
2024-05-07 3:22 ` [PATCH 3/3] btrfs-progs: tests/convert: add test case for ext4 " Qu Wenruo
2024-06-03 20:14 ` [PATCH 0/3] btrfs-progs: convert: proper ext4 unwritten extents handling David Sterba
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=CAE0VrX+tqJ3t3Hmu5wE9fCk2RvgNvEE7UpFs2UVVo02-Zd7+rw@mail.gmail.com \
--to=y16267966@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).