On Sun, Dec 11, 2016 at 4:30 PM, Markus Binsteiner <mak...@gmail.com> wrote: >> OK when I do it on a file system with just 14GiB of metadata it's >> maybe 15 seconds. So a few minutes sounds sorta suspicious to me but, >> *shrug* I don't have a file system the same size to try it on, maybe >> it's a memory intensive task and once the system gets low on RAM while >> traversing the file system it slows done a ton. > > Ok, thanks, looks like there is some other issue then as well. The > process doesn't take up any memory at all, just 100% of one core. > > Maybe I'll try to use it with an older version of btrfs-progs, from > Debian Jessie. Don't think it'll make any difference, but I don't know > what else to try. At this point I'm more curious than anything else. > I've got backups for most of my stuff, just a few rogue scripts I'd > have to re-write. Still, would be nice to get those back.
You might try 'btrfs check' without repairing, using a recent version of btrfs-progs and see if it finds anything unusual. Although, are there many snapshots? That would cause the rentention of roots. -- 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