One of my patch addressed a problem that a converted btrfs can't pass
btrfsck.
Not sure if that is the cause, but if you can try btrfs-progs v3.19.1,
the one without my btrfs-progs patches and some other newer convert
related patches, and see the result?
I think this would at least provide the base for bisect the btrfs-progs
if the bug is in btrfs-progs.
Thanks,
Qu
Chris Murphy wrote on 2015/07/09 15:38 -0600:
On Thu, Jul 9, 2015 at 4:52 AM, Vytautas D <vyt...@gmail.com> wrote:
<Slightly off topic>
does these bugs exist in systems that converted from ext4 to btrfs using
kernel 3.13 and then upgraded to kernel 4.1 ?
I don't recall what btrfs-progs and kernel I last tested ext4
conversion with. I know this is a regression, I just don't know how
old it is. I think there's more than one bug here (obviously since
I've filed 4 related bugs in ~24 hours), but I really don't know the
scope of the problem. But the case where the recommended procedure not
only fails but corrupts the file system and it can't be fixed or
rolled back, is not good.
Perhaps the wiki should provide a warning that this is currently
broken, status unknown, or something?
--
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
