From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [Patch 10/44] fsck.gfs2: Keep di_nlink in sync when adding links for lost+found
Date: Fri, 12 Aug 2011 10:24:08 +0100 [thread overview]
Message-ID: <1313141048.2704.27.camel@menhir> (raw)
In-Reply-To: <1745424561.544679.1313096513973.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
Looks good,
Steve.
On Thu, 2011-08-11 at 17:01 -0400, Bob Peterson wrote:
> >From da57639e65b148bb4d2a3c6a9d98623b8ad18b04 Mon Sep 17 00:00:00 2001
> From: Bob Peterson <rpeterso@redhat.com>
> Date: Mon, 8 Aug 2011 14:21:06 -0500
> Subject: [PATCH 10/44] fsck.gfs2: Keep di_nlink in sync when adding links for
> lost+found
>
> When adding a ".." entry to a directory newly linked to lost+found
> fsck.gfs2 needs to update its di_nlink value to account for the new
> link. If not, it can "correct" the di_nlink value to the wrong
> value and not find the error until a second fsck.gfs2 is done.
> This only happens in the rare case where there is no pre-existing
> ".." entry that may be reused to re-link to lost+found.
>
> rhbz#675723
> ---
> gfs2/fsck/lost_n_found.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/gfs2/fsck/lost_n_found.c b/gfs2/fsck/lost_n_found.c
> index 32f3c5c..b6f02b9 100644
> --- a/gfs2/fsck/lost_n_found.c
> +++ b/gfs2/fsck/lost_n_found.c
> @@ -118,6 +118,7 @@ int add_inode_to_lf(struct gfs2_inode *ip){
> dip = fsck_load_inode(sdp, di->dotdot_parent);
> if (dip->i_di.di_nlink > 0) {
> dip->i_di.di_nlink--;
> + set_di_nlink(dip); /* keep inode tree in sync */
> log_debug(_("Decrementing its links to %d\n"),
> dip->i_di.di_nlink);
> bmodified(dip->i_bh);
> @@ -128,6 +129,7 @@ int add_inode_to_lf(struct gfs2_inode *ip){
> "Changing it to 0.\n"),
> dip->i_di.di_nlink);
> dip->i_di.di_nlink = 0;
> + set_di_nlink(dip); /* keep inode tree in sync */
> bmodified(dip->i_bh);
> }
> fsck_inode_put(&dip);
prev parent reply other threads:[~2011-08-12 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 21:01 [Cluster-devel] [Patch 10/44] fsck.gfs2: Keep di_nlink in sync when adding links for lost+found Bob Peterson
2011-08-12 9:24 ` Steven Whitehouse [this message]
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=1313141048.2704.27.camel@menhir \
--to=swhiteho@redhat.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;
as well as URLs for NNTP newsgroup(s).