cluster: RHEL510 - fsck.gfs2: Increment link count reporting wrong dinode

[Bob Peterson]

Gitweb:        http://git.fedorahosted.org/git/?p=cluster.git;a=commitdiff;h=bd252744f5297a...
Commit:        bd252744f5297a2a2d38baa32cf21acf802fbc83
Parent:        96652b11c13dec9672162211d0c98bb7ec6b46b5
Author:        Bob Peterson 
AuthorDate:    Fri Jan 6 14:11:11 2012 -0600
Committer:     Bob Peterson 
CommitterDate: Fri Apr 5 06:25:00 2013 -0700

fsck.gfs2: Increment link count reporting wrong dinode

The output from fsck.gfs2 was wrong when it reported about a
link count change for lost+found.  This patch fixes the message
so it reports the correct dinode block number.

rhbz#877150
---
 gfs2/fsck/lost_n_found.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/gfs2/fsck/lost_n_found.c b/gfs2/fsck/lost_n_found.c
index fd3b689..b762f09 100644
--- a/gfs2/fsck/lost_n_found.c
+++ b/gfs2/fsck/lost_n_found.c
@@ -210,7 +210,7 @@ int add_inode_to_lf(struct gfs2_inode *ip){
    /* If it's a directory, lost+found is back-linked to it via .. */
    if (S_ISDIR(ip->i_di.di_mode))
    	incr_link_count(lf_dip->i_di.di_num.no_addr,
-				ip->i_di.di_mode, _("to lost+found"));
+				ip->i_di.di_num.no_addr, _("to lost+found"));

log_notice( _("Added inode #%llu (0x%llx) to lost+found\n"),
    	    (unsigned long long)ip->i_di.di_num.no_addr,