All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Collins <paul-dsjeNyW6Qm/D+ROgJ3VA+kB+6BGkLq7r@public.gmane.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	"Linux NFS Mailing List" <linux-nfs@vger.kernel.org>,
	"Rasmus Bøg Hansen"
	<rasmus-tUP8e6pgWdNlY7y4Fx5NiA@public.gmane.org>,
	492970@bugs.debian.org, "Christian Surchi" <csurchi@debian.org>,
	"Linux NFSv4 mailing list" <nfsv4@linux-nfs.org>
Subject: Re: (was: nfs-utils-1.1.3 released)
Date: Tue, 05 Aug 2008 08:55:06 +1200	[thread overview]
Message-ID: <87d4ko5wlx.fsf@burly.wgtn.ondioline.org> (raw)
In-Reply-To: <60C652E1-512E-484A-874E-01997B688505@oracle.com> (Chuck Lever's message of "Mon, 4 Aug 2008 11:32:45 -0400")

Chuck Lever <chuck.lever@oracle.com> writes:

> On Aug 3, 2008, at 11:10 AM, J. Bruce Fields wrote:
>> On Mon, Aug 04, 2008 at 12:37:19AM +1200, Paul Collins wrote:
>>> "J. Bruce Fields" <bfields@fieldses.org> writes:
>>>
>>>> On Fri, Aug 01, 2008 at 11:15:33PM +1000, An=C3=ADbal Monsalve Sal=
azar
>>>> wrote:
>>>>> On Mon, Jul 28, 2008 at 03:13:19AM -0400, Steve Dickson wrote:
>>>>>> I just cut the 1.1.3 nfs-utils release. Unfortunately I'm having
>>>>>> issues accessing my kernel.org account so for the moment the
>>>>>> tar ball is only available on SourceForge:
>>>>>>
>>>>>>    http://sourceforge.net/projects/nfs
>>>>>> [...]
>>>>>
>>>>> 1.1.3 clients don't work with a 1.0.10 server anymore.
>>>>
>>>> Very weird--it might make sense if upgrading nfs-utils broke the
>>>> mount
>>>> itself, but here it seems the mount is succeeding and subsequent
>>>> file
>>>> access (which I'd expect to only involve the in-kernel client
>>>> code) is
>>>> failing.  Maybe there's some difference in the mount options?
>>>> What does
>>>> /proc/self/mounts say?  I assume these are all v2 or v3 mounts?
>>>
>>> I discovered today that I was no longer able to write to the v3
>>> mount on
>>> my 1.1.2 server.  I checked /proc/mounts and noticed sec=3Dnull on =
the
>>> mount.  Either adding sec=3Dsys to the client's mount options or
>>> downgrading to nfs-common 1.1.2 on the client fixes the problem.
>>
>> That would do it!
>>
>> So it sounds like there's a bug that causes mount.nfs to get the
>> default
>> mount options wrong?
>
> I'm not sure I'm following this.  I can't think of a user-space
> mount.nfs change in 1.1.3 that would affect the sec=3D option.
>
> Paul, which kernel are you running on your clients?

Either 2.6.26 or 2.6.27-rc1+.  I'll double-check.

Whichever one it was, the problem was present with 1.1.3 installed, and
not present with 1.1.2 installed.

--=20
Paul Collins
Wellington, New Zealand

Dag vijandelijk luchtschip de huismeester is dood

  reply	other threads:[~2008-08-04 20:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28  7:13 nfs-utils-1.1.3 released Steve Dickson
2008-07-29 17:21 ` Steve Dickson
2008-08-01 13:15 ` (was: nfs-utils-1.1.3 released) Aníbal Monsalve Salazar
     [not found]   ` <20080801131533.GN14057-ePWG1nzy00eujY+JMLXK6WCv5UukjcD9wsqeKsqY1Ps@public.gmane.org>
2008-08-02 17:25     ` J. Bruce Fields
     [not found]   ` <20080802172529.GC30454@fieldses.org>
2008-08-03 11:43     ` Neil Brown
2008-08-03 12:37     ` Paul Collins
     [not found]       ` <87myjul1fk.fsf-D7l3p2TGOOdLdt5/z87VRY6ehsQQaF5K@public.gmane.org>
2008-08-03 15:10         ` J. Bruce Fields
2008-08-04 15:32           ` Chuck Lever
2008-08-04 20:55             ` Paul Collins [this message]
     [not found]               ` <87d4ko5wlx.fsf-D7l3p2TGOOdLdt5/z87VRY6ehsQQaF5K@public.gmane.org>
2008-08-05 15:20                 ` Chuck Lever
2008-08-05 19:28                   ` Bug#492970: " Rasmus Bøg Hansen
2008-08-06 16:21                     ` Chuck Lever
2008-08-06 18:21                       ` Sergey Bolshakov
2008-08-06 21:24                         ` (was: nfs-utils-1.1.3 released) Chuck Lever
2008-08-07 15:05                       ` Bug#492970: " Lucas Nussbaum
2008-08-07 16:29                         ` Chuck Lever
2008-08-09  1:06                           ` Chuck Lever
2008-08-10 21:40                             ` J. Bruce Fields
2008-08-26 11:10                             ` Aníbal Monsalve Salazar

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=87d4ko5wlx.fsf@burly.wgtn.ondioline.org \
    --to=paul-dsjenyw6qm/d+rogj3va+kb+6bgklq7r@public.gmane.org \
    --cc=492970@bugs.debian.org \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=csurchi@debian.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.org \
    --cc=rasmus-tUP8e6pgWdNlY7y4Fx5NiA@public.gmane.org \
    /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.