From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Price <anprice@redhat.com>
Date: Tue, 16 Jul 2013 17:52:20 +0100
Subject: [Cluster-devel] [gfs2-utils PATCH 5/7] fsck.gfs2: don't check
 newly created lost+found in pass2
In-Reply-To: <146e1e3ee8e8c3fe6b5055a584ab987a49a0a85f.1373979296.git.rpeterso@redhat.com>
References: <08b2ef646a21c19d0cdd1212fe8d4b4a8d7ee2b2.1373979296.git.rpeterso@redhat.com>
	<146e1e3ee8e8c3fe6b5055a584ab987a49a0a85f.1373979296.git.rpeterso@redhat.com>
Message-ID: <51E57A44.6000802@redhat.com>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Bob,

 > --- a/gfs2/fsck/pass2.c
> +++ b/gfs2/fsck/pass2.c
> @@ -1683,6 +1683,14 @@ int pass2(struct gfs2_sbd *sdp)
>   		if (q != gfs2_inode_dir)
>   			continue;
>
> +		/* If we created lost+found, its links should have been
> +		   properly adjusted, so don't check it. */
> +		if (lf_was_created &&
> +		    (dirblk == lf_dip->i_di.di_num.no_addr)) {
> +			log_debug("Pass2 skipping the new new lost+found.\n");

Spotted "new new" here but maybe it needs _() also.

Cheers,
Andy