Dear Michael, On Thu, Jun 15, 2017 at 09:12:28AM +0800, Michael Tsang wrote: > Package: btrfs-progs > Version: 4.7.3-1 > Severity: important [...] > -- System Information: > Debian Release: 9.0 > APT prefers testing > APT policy: (990, 'testing'), (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores) > Locale: LANG=en_HK.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), > LANGUAGE=en_HK:en_GB:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system)
I'm not the maintainer of Debian's btrfs-progs, but I couldn't help noticing that you were running linux-3.16.x (from Debian 8/jessie) at the time of the attempted btrfs-convert operation. It was only after linux-4.4 that I found that anything btrfs-related became more likely to succeed than to fail. What happens if you try this after booting to Debian 9/stretch's 4.9.x kernel? Personally I wouldn't attempt to use btrfs-convert until late 2018, and only after upstream begins to recommended it as a viable alternative to mkfs.btrfs. That said, I'd love to be wrong, and to discover that stretch's btrfs-progs and kernel will convert ext successfully--and more importantly, will convert to a volume that won't self-destruct. :-) Looking forward to hearing of your success, Nicholas
signature.asc
Description: PGP signature
