On 10 December 2014 at 13:47, Duncan <1i5t5.dun...@cox.net> wrote: > > The recursive btrfs defrag after deleting the saved ext* subvolume > _should_ have split up any such > 1 GiB extents so balance could deal > with them, but either it failed for some reason on at least one such > file, or there's some other weird corner-case going on, very likely > something else having to do with the conversion.
I've run defrag several times again and it doesn't do anything additional. > Patrik, assuming no btrfs snapshots yet, can you do a du --all --block- > size=1M | sort -n (or similar), then take a look at all results over 1024 > (1 GiB since the du specified 1 MiB blocks), and see if it's reasonable > to move all those files out of the filesystem and back? Good idea, but it's quite a lot of files. I'd rather start over. But I've identified 46 files from Btrfs errors in syslog and will try to move them to another disk. They're ranging from 41KiB to 6.6GiB in size. Is btrfs-debug-tree -e useful in finding problematic files? -- 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
