Cluster-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] NFS v2 not compatible with GFS2
Date: Wed, 08 Apr 2009 16:23:18 +0100	[thread overview]
Message-ID: <1239204198.3359.44.camel@localhost.localdomain> (raw)
In-Reply-To: <f4f856dc0904080816s558fb77am3292111e4823a53f@mail.gmail.com>

Hi,

On Wed, 2009-04-08 at 08:16 -0700, Craig Johnston wrote:
> On Wed, Apr 8, 2009 at 1:54 AM, Steven Whitehouse <swhiteho@redhat.com> wrote:
> >
> > Hi,
> >
> > On Tue, 2009-04-07 at 13:04 -0700, Craig Johnston wrote:
> > > We have found that NFS version 2 does not seem to be compatible with
> > > an NFS exported GFS2 file system.  The NFS client can mount the file
> > > system, but any file I/O results in Stale File Handle and I/O errors.
> > >
> > > It looks very much like the problem described here -
> > > https://bugzilla.redhat.com/show_bug.cgi?id=229345
> > >
> > > Has there been any progress on resolving this issue, or are we out of
> > > luck.  We have a legacy device that will only use NFS v2, and we would
> > > very much like to use GFS2 as we do for the rest of our system.
> > >
> > > To replicate the problem for a GFS2 exported file system (say
> > > /data/mygfs2_fs on host foo ), mount it on another host as
> > > "% mount -o nfsvers=2 foo:/data/mygfs2_fs /mnt/tmp"
> > >
> > > You will find that you can list the directory entries, but any attempt
> > > to read or write to files will fail.
> > >
> > > Note, we find that the GFS file system does not seem to have problems
> > > with NFS v2 clients, only GFS2.
> > >
> > > Any help would be appreciated.
> > > Craig
> > >
> > Yes, it is a bug inherited from GFS. GFS2 uses the same filehandles
> > (i.e. too large for NFSv2) so that for the time being, only NFSv3+ will
> > work with GFS2. I don't know why GFS appears to work and GFS2 doesn't -
> > they should be identical in that respect,
> >
> > Steve.
> >
> >
> Bummer.  This is a capability we we really need, as we have to
> interface with some older systems running VxWorks that only supports
> NFS v2.  We have verified that GFS supports NFS v2.  Does this mean
> there is hope that GFS2 could also support NFS v2 since they use the
> same filehandles?  Where should I start poking around if I wanted to
> delve into the source?
> 
> Thanks,
> Craig

By all means have a look in the source. I suspect that there would be
issues if you ever had a filesystem larger than 2^32 blocks with GFS
using the NFSv2 handles. It might just be silently ignoring that issue,
so I'd be careful.

I would like to see NFSv2 working with GFS2, so I'd be happy to accept
patches if you can work out how to stuff all the required information
into such a small file handle. Also it would need to leave the existing
file handles for NFSv3 alone as we must not change that format in an
incompatible way.

All the code is easy to find in ops_export.c and its all self-contained
in that file,

Steve.




  reply	other threads:[~2009-04-08 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07 20:04 [Cluster-devel] NFS v2 not compatible with GFS2 Craig Johnston
2009-04-08  8:54 ` Steven Whitehouse
2009-04-08 15:16   ` Craig Johnston
2009-04-08 15:23     ` Steven Whitehouse [this message]
2009-04-17 22:07       ` agspoon
2009-04-21 12:11         ` Steven Whitehouse

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=1239204198.3359.44.camel@localhost.localdomain \
    --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