From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] - Bug 537201 - Better error reporting when mounting a gfs fs without enough journals
Date: Mon, 08 Feb 2010 10:57:18 +0000 [thread overview]
Message-ID: <1265626638.2817.2.camel@localhost> (raw)
In-Reply-To: <140473617.1142161265412341507.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
Hi,
Now in the GFS2 -nmw git tree. Thanks,
Steve.
On Fri, 2010-02-05 at 18:25 -0500, Abhijith Das wrote:
> Please ignore the previous patch. The patch inlining didn't work right. Here's the unmangled one.
>
> --Abhi
>
> ----- "Abhijith Das" <adas@redhat.com> wrote:
>
> > From: "Abhijith Das" <adas@redhat.com>
> > To: "cluster-devel" <cluster-devel@redhat.com>
> > Sent: Friday, February 5, 2010 5:17:56 PM GMT -06:00 US/Canada Central
> > Subject: [Cluster-devel] [GFS2 PATCH] - Bug 537201 - Better error reporting when mounting a gfs fs without enough
> > journals
> >
> > Hi,
> >
> > We need this one-liner to signal the mount helper of the 'insufficient
> > journals' condition.
> >
> > Signed-off-by: Abhijith Das <adas@redhat.com>
> >
> > diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
> > index d405c38..a054b52 100644
> > --- a/fs/gfs2/ops_fstype.c
> > +++ b/fs/gfs2/ops_fstype.c
> > @@ -724,7 +724,7 @@ static int init_journal(struct gfs2_sbd *sdp, int
> > undo)
> > goto fail;
> > }
> >
> > - error = -EINVAL;
> > + error = -EUSERS;
> > if (!gfs2_jindex_size(sdp)) {
> > fs_err(sdp, "no journals!\n");
> > goto fail_jindex;
next prev parent reply other threads:[~2010-02-08 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1794011848.1142141265412324522.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2010-02-05 23:25 ` [Cluster-devel] [GFS2 PATCH] - Bug 537201 - Better error reporting when mounting a gfs fs without enough journals Abhijith Das
2010-02-08 10:57 ` Steven Whitehouse [this message]
2010-02-05 23:17 Abhijith Das
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=1265626638.2817.2.camel@localhost \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.