linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Zangl <coralllama@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: "missing data block" when converting ext4 to btrfs
Date: Mon, 13 Jul 2020 21:46:35 +0200	[thread overview]
Message-ID: <90fff9c0-36c5-d45c-d19b-01294fc93b1e@gmail.com> (raw)

I am on a test VM where I am trying to convert a second disk to btrfs.

The conversion fails with the error missing data block for bytenr 
1048576 (see below).

I couldn't find any information about the error. What can I do to fix this?

$ fsck -f /dev/sdb1
fsck from util-linux 2.35.2
e2fsck 1.45.6 (20-Mar-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdb1: 150510/4194304 files (0.5% non-contiguous), 2726652/16777216 
blocks

$ btrfs-convert /dev/sdb1
create btrfs filesystem:
         blocksize: 4096
         nodesize:  16384
         features:  extref, skinny-metadata (default)
         checksum:  crc32c
creating ext2 image file
ERROR: missing data block for bytenr 1048576
ERROR: failed to create ext2_saved/image: -2
WARNING: an error occurred during conversion, filesystem is partially 
created but not finalized and not mountable

$ uname -a
Linux t-arch 5.7.7-arch1-1 #1 SMP PREEMPT Wed, 01 Jul 2020 14:53:16 
+0000 x86_64 GNU/Linux

$ btrfs --version
btrfs-progs v5.7

             reply	other threads:[~2020-07-13 19:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 19:46 Christian Zangl [this message]
2020-07-14  6:10 ` "missing data block" when converting ext4 to btrfs 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
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=90fff9c0-36c5-d45c-d19b-01294fc93b1e@gmail.com \
    --to=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;
as well as URLs for NNTP newsgroup(s).