From: Nikolay Borisov <nborisov@suse.com>
To: "Torbjörn Jansson" <torbjorn@jansson.tech>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-convert aborts with an assert
Date: Mon, 6 Jun 2022 17:14:56 +0300 [thread overview]
Message-ID: <b4211a54-c491-2b8f-8586-efb8c570bba3@suse.com> (raw)
In-Reply-To: <023b5ca9-0610-231b-fc4e-a72fe1377a5a@jansson.tech>
On 6.06.22 г. 17:03 ч., Torbjörn Jansson wrote:
> Hello
>
> i tried to do a btrfs-convert of a ext4 filesystem and after a short
> while after starting it i was greeted with:
>
> # btrfs-convert /dev/xxxx
> btrfs-convert from btrfs-progs v5.16.2
>
> convert/main.c:1162: do_convert: Assertion `cctx.total_bytes != 0`
> failed, value 0
> btrfs-convert(+0xffb0)[0x557defdabfb0]
> btrfs-convert(main+0x6c5)[0x557defdaa125]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea)[0x7f66e1f8bd0a]
> btrfs-convert(_start+0x2a)[0x557defdab52a]
> Aborted
>
> Any idea whats going on?
> Is it a known bug?
> Is the btrfs-progs that come with my dist too old?
> FYI the ext4 filesystem is a bit large ~10tb of used data on it.
>
> I assume the convert didn't even start in this case and nothing was
> modified on the ext4 filesystem, correct? or?
>
This suggests that btrfs progs is unable to properly read/parse the
superblock of the ext4 filesystem. So you are right that convert hasn't
even started in this case so your ext4 is intact.
However, that's strange since for ext* related queries we do use libext2fs.
next prev parent reply other threads:[~2022-06-06 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 14:03 btrfs-convert aborts with an assert Torbjörn Jansson
2022-06-06 14:14 ` Nikolay Borisov [this message]
2022-06-06 14:31 ` Nikolay Borisov
2022-06-06 15:00 ` Torbjörn Jansson
2022-06-06 15:21 ` Nikolay Borisov
2022-06-06 15:31 ` Torbjörn Jansson
2022-06-07 18:24 ` Chris Murphy
2022-06-09 17:55 ` Torbjörn Jansson
2022-06-06 14:34 ` 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=b4211a54-c491-2b8f-8586-efb8c570bba3@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=torbjorn@jansson.tech \
/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