This is completely reproducible with a brand new file system created as raid1, using kernel 3.19 and btrfs-progs 3.18. The conversion from raid1 to single, if paused, will apparently break the file system's ability to be subsequently mounted writable. And further, btrfs-image fails. I've updated the bug report. https://bugzilla.kernel.org/show_bug.cgi?id=92641 First, the conversion from data/metadata raid1 should be faster than requiring fully reading and writing the file system. As this is a 2 device raid1, each is already effectively data/metadata single, so I'm not sure why anything other than metadata needs rewriting. Second, either what I'm doing should be disallowed (user can't force conversion of a degraded array to single), or the file system shouldn't break like this. Third, the error message is confusing "too many missing devices, writeable mount is not allowed" the first part of that is definitely not true. How can there be too many missing devices when it started out as a 2 device volume and the remaining device isn't an ro or seed device? Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
