From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bob Peterson Date: Fri, 17 May 2013 08:47:12 -0400 (EDT) Subject: [Cluster-devel] [gfs2-utils PATCH 06/47] fsck.gfs2: Check for formal inode mismatch when adding to lost+found In-Reply-To: <1368634104.2732.104.camel@menhir> References: <9b5bd520e0fce30d15dfa53e3d549f34d5c8a696.1368548305.git.rpeterso@redhat.com> <1368634104.2732.104.camel@menhir> Message-ID: <1927440696.13152052.1368794832429.JavaMail.root@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit ----- Original Message ----- | Hi, | | On Tue, 2013-05-14 at 11:21 -0500, Bob Peterson wrote: | > This patch adds a check to the code that adds inodes to lost+found | > so that dinodes with formal inode mismatches are logged, but not added. | > | I'm not sure I understand what this one is doing. If there is a mismatch | between the dir entry and the inode that suggests that the dir entry and | inode are not related to the same thing, | | Steve. Hi, Yes, you're correct, and this mismatch is precisely why it's wrong to add the file to lost+found, and that's what this patch is avoiding. Regards, Bob Peterson Red Hat File Systems