From: Anand Jain <anand.jain@oracle.com>
To: jordan.j@mail.bg, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-convert on 24Gb image corrupts files.
Date: Sun, 5 May 2024 08:56:24 +0800 [thread overview]
Message-ID: <0fbad9f2-6f26-4fcb-ac8e-a1fa4ebc80db@oracle.com> (raw)
In-Reply-To: <d34c7d77a7f00c93bea6a4d6e83c7caf.mailbg@mail.bg>
> on ext4:
>
> ilefrag -v
> m/root/.mozilla/firefox/s554srh9.default-release/storage/permanent/chrome/idb/3561288849sdhlie.sqlite
> Filesystem type is: ef53
> File size of
> m/root/.mozilla/firefox/s554srh9.default-release/storage/permanent/chrome/idb/3561288849sdhlie.sqlite is 49152 (12 blocks of 4096 bytes)
> ext: logical_offset: physical_offset: length: expected:
> flags:
> 0: 0.. 1: 2217003.. 2217004: 2:
> 1: 2.. 10: 2217019.. 2217027: 9: 2217005:
> 2: 11.. 11: 2217028.. 2217028: 1:
> last,unwritten,eof
> m/root/.mozilla/firefox/s554srh9.default-release/storage/permanent/chrome/idb/3561288849sdhlie.sqlite: 2 extents found
>
btrfs-convert doesn't support ext4's "unwritten" extents. V2 of the fix
is in progress.
[PATCH 0/4] btrfs-progs: add support ext4 unwritten file extent
Thanks, Anand
next prev parent reply other threads:[~2024-05-05 0:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 0:34 btrfs-convert on 24Gb image corrupts files jordan.j
2024-05-05 0:50 ` Qu Wenruo
2024-05-05 0:56 ` Anand Jain [this message]
2024-05-05 5:54 ` Qu Wenruo
2024-05-06 0:33 ` Anand Jain
-- strict thread matches above, loose matches on Subject: below --
2024-05-05 15:05 Yordan
2024-05-05 22:31 ` Qu Wenruo
2024-05-05 22:30 You can reproduce it yourself now Yordan
2024-05-06 10:53 ` btrfs-convert on 24Gb image corrupts files Yordan
2024-05-06 13:17 ` Anand Jain
2024-05-06 13:35 ` Yordan
2024-05-06 13:43 ` Anand Jain
2024-05-06 14:57 ` Yordan
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=0fbad9f2-6f26-4fcb-ac8e-a1fa4ebc80db@oracle.com \
--to=anand.jain@oracle.com \
--cc=jordan.j@mail.bg \
--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