-------- Original Message --------
Subject: Re: [PATCH 0/6] More generic inode nlink repair function
From: David Sterba <dsterba@xxxxxxx>
To: Qu Wenruo <quwenruo@xxxxxxxxxxxxxx>
Date: 2014年12月05日 01:20
On Wed, Dec 03, 2014 at 03:41:19PM +0800, Qu Wenruo wrote:
How about making lost+found on mkfs.btrfs like ext4?
I hope most user won't see the lost+found dir.
...
So lost+found should only occur when it is needed, and when it is needed
it will be created.
Ack, as was mentioned before, lost+found is local to the containing
subvolume so creating one for the whole filesystem at mkfs time is of no
use.
The usecase for creating the directory (compared to copying the files
somewhere else) is to give a direct access to the files once the
repaired filesystem is mounted again. Both should be implemented in the
end.
Understood.
I'll also try if there is anything that can help btrfs-restore and
backport it to restore later,
hoping later btrfsck patches can help both restore and btrfsck --repair.
Thanks,
Qu
--
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
