All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: "Brandon D. Valentine" <brandon@dvalentine.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [bug] FC2/2.6.8.1 does not fallback to NFSv2
Date: Sat, 28 Aug 2004 21:31:10 +0100	[thread overview]
Message-ID: <4130EB8E.6000609@moving-picture.com> (raw)
In-Reply-To: <20040828195703.GB84014@brandon.dvalentine.com>

Brandon D. Valentine wrote:
> On Sat, Aug 28, 2004 at 02:45:22PM -0400, Trond Myklebust wrote:
> 
> I applied the patch James Pearson also posted to this thread to the
> SRPM, and it allowed me to mount the filesystem.
> 
>   [root@scylla mount]# ./mount -t nfs reef:/export/reef/httpd/ /mnt/temp/
>   Probed program 100003, vers 3, (udp) with result 9
>   Probed program 100003, vers 2, (udp) with result 0
>   Probed program 100005, vers 1, (tcp) with result 0
>   [root@scylla mount]# grep reef /proc/mounts
>   reef:/export/reef/httpd/ /mnt/temp nfs rw,v2,rsize=8192,wsize=8192,hard,udp,lock,addr=reef 0 0
> 
> Out of curiosity I just grabbed the upstream util-linux-2.12b tarball
> and built it and was also able to mount the filesystem no problem, so
> this bug definitely seems to be a bug in the RedHat SRPM.  Their version
> of nfsmount.c is vastly different from the upstream version.

Yes, its definitely a bug in Redhat's version - a bugzilla comment says 
'Patch added to CVS for the next util-linux package' - as yet, this 
doesn't seem to have been released yet.

It appears that a lot of the changes in their nfsmount.c are based on a 
patch that has been on Trond's site for sometime - 
http://client.linux-nfs.org/util-linux-2.11n.dif.gz (although, not the 
bit that causes it to fail to fall back to NFSv2!)

> 
>   [root@scylla mount]# ./mount -t nfs reef:/export/reef/httpd/ /mnt/temp/
>   [root@scylla mount]# grep reef /proc/mounts 
>   reef:/export/reef/httpd/ /mnt/temp nfs rw,v2,rsize=8192,wsize=8192,hard,udp,lock,addr=reef 0 0
> 
> Thanks for all of your help.  I guess from here on out I've gotta take
> it up with the RPM maintainer.

May be someone on this list from RedHat can help ...

James Pearson



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-08-28 20:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27 21:22 [bug] FC2/2.6.8.1 does not fallback to NFSv2 Brandon D. Valentine
2004-08-27 21:36 ` Trond Myklebust
2004-08-27 21:51   ` Trond Myklebust
2004-08-27 23:32     ` Brandon D. Valentine
2004-08-27 23:34       ` Brandon D. Valentine
2004-08-28  5:35         ` Trond Myklebust
2004-08-28  6:29           ` Brandon D. Valentine
2004-08-28 18:45             ` Trond Myklebust
2004-08-28 19:57               ` Brandon D. Valentine
2004-08-28 20:31                 ` James Pearson [this message]
2004-08-28 17:10       ` Steve Dickson
2004-08-28 18:38         ` Brandon D. Valentine
2004-08-29  1:32           ` Steve Dickson
2004-08-29  2:13             ` Brandon D. Valentine
2004-08-28  9:32 ` raven
2004-08-28 16:47 ` James Pearson

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=4130EB8E.6000609@moving-picture.com \
    --to=james-p@moving-picture.com \
    --cc=brandon@dvalentine.com \
    --cc=nfs@lists.sourceforge.net \
    /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.