Hello,
I have been seeing this behavior (on the unmounted filesystem, of course!):
date && time btrfs-convert /dev/mapper/bakfs
Sat Oct 12 23:13:21 CDT 2013
creating btrfs metadata.
error during copy_inodes -1
conversion aborted.
real 43m1.076s
user 15m25.256s
sys 0m21.508s
This is 100% reproducible on this volume. It passes fsck.ext4 -f with
no errors, and I can detect nothing wrong. This is on a Debian backport
of kernel 3.10 on i686 32-bit. The filesystem in question is 2.7T in
size, with 908G free. It is a target for BackupPC, and as such has
many, many hardlinks and inodes in use due to the BackupPC hardlink
pool. Some files may be hardlinked to hundreds of others as well. (A
quick spot-guess revealed one with 418 hardlinks. There may be some
with more.) I didn't capture df -ih output when I should have, but the
number of inodes was between 30M and 40M. The underlying device is an
LVM RAID0 across two USB drives - so a slow device, but it has always
worked perfectly. There are no kernel errors involved here.
The btrfs-tools is 0.19+20130705 plus the patch from
https://patchwork.kernel.org/patch/2828820/ to address the "No valid
Btrfs found" bug I encountered, which was reported at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724265 and various
other places.
What can I do to help with the debugging of this?
Thanks,
John
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
