[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Cluster-devel] [PATCH 50/56] fsck.gfs2: Increment link count reporting wrong dinode



>From 878f33b79259b6798f19c3569278b46a170eee10 Mon Sep 17 00:00:00 2001
From: Bob Peterson <rpeterso redhat com>
Date: Tue, 23 Aug 2011 09:28:22 -0500
Subject: [PATCH 50/56] 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#675723
---
 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 2579480..625de0d 100644
--- a/gfs2/fsck/lost_n_found.c
+++ b/gfs2/fsck/lost_n_found.c
@@ -282,7 +282,7 @@ int add_inode_to_lf(struct gfs2_inode *ip){
 	/* If it's a directory, lost+found is back-linked to it via .. */
 	if (is_dir(&ip->i_di, sdp->gfs1))
 		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,
-- 
1.7.4.4


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]