2015-12-11 21:24 GMT+03:00 Chris Murphy <lists@xxxxxxxxxxxxxxxxx>: > I would not repair it if the risk of it getting worse is bad for your data. > > Note the wiki says this feature is not well tested and is reported to > not work reliably. > https://btrfs.wiki.kernel.org/index.php/Conversion_from_Ext3 > > Qu is working on patches to fix some of these problems, I don't know > the status of any of that. I just did a conversion myself the other > day with kernel 4.4.0rc3 and btrfs-progs 4.3.1 and that worked without > error. But there were also no big files at all (it was just a clean OS > installation). I immediately took a snapshot of that, and btrfs > send/receive it to a new Btrfs volume, and then discarded the > converted one entirely. > > The trace looks like it's mounting read-only? If it can be mounted > read only, get the important data off the volume if it's not already > backed up, and then blow it away. I personally wouldn't bother with > repairing it. What is the better way to get data? send/receive works only with RO snapshots. Is there another way to preserve subvolumes and CoW structure (a lot of files was copied between subvols using "cp --reflink=always")? Or just rsync'ing files is all what I can do? -- 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
