From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <dsterba@suse.cz>,
Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>,
Ed Tomlinson <edt@aei.ca>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/6] More generic inode nlink repair function
Date: Fri, 5 Dec 2014 09:11:56 +0800 [thread overview]
Message-ID: <5481065C.8090901@cn.fujitsu.com> (raw)
In-Reply-To: <20141204172022.GG9754@twin.jikos.cz>
-------- Original Message --------
Subject: Re: [PATCH 0/6] More generic inode nlink repair function
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
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
next prev parent reply other threads:[~2014-12-05 1:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 4:18 [PATCH 0/6] More generic inode nlink repair function Qu Wenruo
2014-12-03 4:18 ` [PATCH RESEND 1/6] btrfs-progs: print root dir verbose error in fsck Qu Wenruo
2014-12-03 4:18 ` [PATCH RESEND 2/6] btrfs-progs: Import btrfs_insert/del/lookup_extref() functions Qu Wenruo
2014-12-03 4:18 ` [PATCH RESEND 3/6] btrfs-progs: Import lookup/del_inode_ref() function Qu Wenruo
2014-12-03 4:18 ` [PATCH v3 4/6] btrfs-progs: Add btrfs_unlink() and btrfs_add_link() functions Qu Wenruo
2014-12-03 4:18 ` [PATCH RESEND v2 5/6] btrfs-progs: Add btrfs_mkdir() function for the incoming 'lost+found' fsck mechanism Qu Wenruo
2014-12-03 4:18 ` [PATCH v2 6/6] btrfs-progs: Add fixing function for inodes whose nlink dismatch Qu Wenruo
2014-12-03 14:30 ` Ed Tomlinson
2014-12-03 5:03 ` [PATCH 0/6] More generic inode nlink repair function Ed Tomlinson
2014-12-03 7:12 ` Satoru Takeuchi
2014-12-03 7:41 ` Qu Wenruo
2014-12-04 17:20 ` David Sterba
2014-12-05 1:11 ` Qu Wenruo [this message]
2014-12-04 17:27 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5481065C.8090901@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--cc=edt@aei.ca \
--cc=linux-btrfs@vger.kernel.org \
--cc=takeuchi_satoru@jp.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox