On Oct 27, 2014, at 10:54 AM, Jasper Verberk <jverb...@hotmail.com> wrote:
> I actually tried going to raid1 with kernel 3.10 before....the reason I > updated to 3.17 was to see if this would fix the error. > > It still remained though…. If you have btrfs-progs you could do a btrfs check without repair and see if that's enlightening. Can you do a normal balance successfully, without conversion? If you haven't tried it recently with a newer kernel you might try for starters: btrfs balance start -musage=100 -dusage=50 Any data chunks less than 50% full will be balanced, and all the metadata chunks will be balanced. This line: Data, RAID1: total=2.85TiB, used=790.46GiB Is suspiciously high for allocated chunks compared to the data stored in it. Maybe releasing some chunks will solve the problem and permit conversion to proceed. Chris Murphy-- 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
