It seems I've accidentally deleted all files in my home directory, which sits in its own btrfs partition (lvm on luks). Now I'm trying to find the roots to be able to use btrfs restore later on.
btrfs-find-root seems to be taking ages though. I've run it like so: btrfs-find-root /dev/mapper/think--big-home -o 5 > roots.txt After 16 hours, there is still no output, but it's still running utilizing 100% of one core. Is there any way to gauge how much longer it'll take? Should there have been output already while it's running? When I run it without redirecting stdout, I get: $ btrfs-find-root /dev/mapper/think--big-home -o 5 Superblock doesn't contain generation info for root 5 Superblock doesn't contain the level info for root 5 When I omit the '-o 5', it says: $ btrfs-find-root /dev/mapper/think--big-home Superblock thinks the generation is 593818 Superblock thinks the level is 0 Is the latter the way to run it? Did that initially, but that didn't return any results in a reasonable timeframe either. The filesystem was created with Debian Jessie, but I'm using Ubuntu ( btrfs-progs v4.7.3 ) to try to restore the files at the moment. Thanks! -- 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
