From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2: fail mount if journal recovery fails
Date: Tue, 10 Jan 2012 09:48:27 +0000 [thread overview]
Message-ID: <1326188907.2717.8.camel@menhir> (raw)
In-Reply-To: <20120109202920.GD9956@redhat.com>
Hi,
Both patches look good and I've pushed them to the -fixes tree for now,
Steve.
On Mon, 2012-01-09 at 15:29 -0500, David Teigland wrote:
> If the first mounter fails to recover one of the journals
> during mount, the mount should fail.
>
> Signed-off-by: David Teigland <teigland@redhat.com>
> ---
> fs/gfs2/incore.h | 1 +
> fs/gfs2/recovery.c | 3 ++-
> 2 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/fs/gfs2/incore.h b/fs/gfs2/incore.h
> index 59114c5..ad2d05e 100644
> --- a/fs/gfs2/incore.h
> +++ b/fs/gfs2/incore.h
> @@ -434,6 +434,7 @@ struct gfs2_jdesc {
> #define JDF_RECOVERY 1
> unsigned int jd_jid;
> unsigned int jd_blocks;
> + int jd_recover_error;
> };
>
> struct gfs2_statfs_change_host {
> diff --git a/fs/gfs2/recovery.c b/fs/gfs2/recovery.c
> index 80701d1..963b2d7 100644
> --- a/fs/gfs2/recovery.c
> +++ b/fs/gfs2/recovery.c
> @@ -583,6 +583,7 @@ fail_gunlock_j:
>
> fs_info(sdp, "jid=%u: %s\n", jd->jd_jid, (error) ? "Failed" : "Done");
> fail:
> + jd->jd_recover_error = error;
> gfs2_recovery_done(sdp, jd->jd_jid, LM_RD_GAVEUP);
> done:
> clear_bit(JDF_RECOVERY, &jd->jd_flags);
> @@ -611,6 +612,6 @@ int gfs2_recover_journal(struct gfs2_jdesc *jd, bool wait)
> wait_on_bit(&jd->jd_flags, JDF_RECOVERY, gfs2_recovery_wait,
> TASK_UNINTERRUPTIBLE);
>
> - return 0;
> + return wait ? jd->jd_recover_error : 0;
> }
>
prev parent reply other threads:[~2012-01-10 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 20:29 [Cluster-devel] gfs2: fail mount if journal recovery fails David Teigland
2012-01-10 9:48 ` 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=1326188907.2717.8.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).