+1, me too. Converting one partition (containing a device-mapper container with an ext4 filesystem) to btrfs, see: btrfs-convert-and-mount.txt
a btrfs-convert -r works fine, fsck after the rollback returns no issue, the filesystem is mountable and fine. I did this once, with 50GB free space, and ran into this error. Suspicious that maybe there wasn't enough free space for the metadata, I freed up 400GB and ran it again - and this is the output of the second try. One note may be: I typically create my ext4 filesystems with `-O sparse_super`. Including attachments for dump-super, and tree-stats. `btrfs dump-tree` didn't seem to produce any errors (`grep -i 'error' | grep -iv '\<name: .*err'` -- lots of files with "error" in the name). btrfs built with `march=native -O2 -mtune=native` which generally includes some AVX-512 code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869281 Title: btrfs-convert of ext4 yields unmountable FS To manage notifications about this bug go to: https://bugs.launchpad.net/btrfs-tools/+bug/1869281/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
