From: "J. Bruce Fields" <bfields@fieldses.org>
To: Mikael Pettersson <mikpe-1zs4UD6AkMk@public.gmane.org>
Cc: ezk-EX0cT3Az47bauI2f2gSDlQ@public.gmane.org,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [NFS] NFSv2/3 broken exporting/mounting (permission denied) in 2.6.24-rc4
Date: Fri, 7 Dec 2007 10:32:31 -0500 [thread overview]
Message-ID: <20071207153230.GA20872@fieldses.org> (raw)
In-Reply-To: <200712071054.lB7AscVW002471-gq7oiAaKCbRt3AgVzhmPzw@public.gmane.org>
On Fri, Dec 07, 2007 at 11:54:38AM +0100, Mikael Pettersson wrote:
> On Thu, 6 Dec 2007 21:20:41 -0500, Erez Zadok wrote:
> > I get a "permission denied" when trying to mount a localhost nfsv2/3
> > exported volume, on v2.6.24-rc4-124-gf194d13. It works w/ nfsv4 mounting.
> > It worked fine in 2.6.24-rc3. Here's a sequence of ops I tried:
> >
> > # mount -t ext2 /dev/hdb1 /n/lower/b0
> > # exportfs -o no_root_squash,rw localhost:/n/lower/b0
> > # mount -t nfs -o nfsvers=3 localhost:/n/lower/b0 /mnt
>
> I'm seeing something similar too. NFSv3 export of an ext3 partition
> to another machine in my lan fails (client gets permission denied)
> when the server runs 2.6.24-rc4. It worked fine in 2.6.24-rc3.
>
> There's no NFSv4 of any kind on either client or server.
And you're not varying the client at all, you're only changing the
kernel version on the server?
There are literally no commits between v2.6.24-rc3 and v2.6.24-rc4 which
touch fs/nfsd/. What filesystem are you exporting? Are the nfs-utils
versions the same in both cases?
Also, could you get a network trace showing the failure?
--b.
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
WARNING: multiple messages have this Message-ID (diff)
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: ezk@cs.sunysb.edu, linux-kernel@vger.kernel.org,
nfs@lists.sourceforge.net
Subject: Re: NFSv2/3 broken exporting/mounting (permission denied) in 2.6.24-rc4
Date: Fri, 7 Dec 2007 10:32:31 -0500 [thread overview]
Message-ID: <20071207153230.GA20872@fieldses.org> (raw)
In-Reply-To: <200712071054.lB7AscVW002471@harpo.it.uu.se>
On Fri, Dec 07, 2007 at 11:54:38AM +0100, Mikael Pettersson wrote:
> On Thu, 6 Dec 2007 21:20:41 -0500, Erez Zadok wrote:
> > I get a "permission denied" when trying to mount a localhost nfsv2/3
> > exported volume, on v2.6.24-rc4-124-gf194d13. It works w/ nfsv4 mounting.
> > It worked fine in 2.6.24-rc3. Here's a sequence of ops I tried:
> >
> > # mount -t ext2 /dev/hdb1 /n/lower/b0
> > # exportfs -o no_root_squash,rw localhost:/n/lower/b0
> > # mount -t nfs -o nfsvers=3 localhost:/n/lower/b0 /mnt
>
> I'm seeing something similar too. NFSv3 export of an ext3 partition
> to another machine in my lan fails (client gets permission denied)
> when the server runs 2.6.24-rc4. It worked fine in 2.6.24-rc3.
>
> There's no NFSv4 of any kind on either client or server.
And you're not varying the client at all, you're only changing the
kernel version on the server?
There are literally no commits between v2.6.24-rc3 and v2.6.24-rc4 which
touch fs/nfsd/. What filesystem are you exporting? Are the nfs-utils
versions the same in both cases?
Also, could you get a network trace showing the failure?
--b.
next prev parent reply other threads:[~2007-12-07 15:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 10:54 [NFS] NFSv2/3 broken exporting/mounting (permission denied) in 2.6.24-rc4 Mikael Pettersson
2007-12-07 10:54 ` Mikael Pettersson
[not found] ` <200712071054.lB7AscVW002471-gq7oiAaKCbRt3AgVzhmPzw@public.gmane.org>
2007-12-07 15:32 ` J. Bruce Fields [this message]
2007-12-07 15:32 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2007-12-07 2:20 Erez Zadok
[not found] ` <200712070220.lB72Kfqw004530-zop+azHP2WsZjdeEBZXbMidm6ipF23ct@public.gmane.org>
2007-12-07 2:55 ` [NFS] " J. Bruce Fields
2007-12-07 2:55 ` J. Bruce Fields
2007-12-07 20:00 ` Erez Zadok
2007-12-07 20:06 ` J. Bruce Fields
2007-12-07 20:32 ` Erez Zadok
2007-12-07 20:32 ` Erez Zadok
2007-12-07 20:38 ` Valdis.Kletnieks
2007-12-07 20:38 ` Valdis.Kletnieks
[not found] ` <200712072000.lB7K0DZ5013256-zop+azHP2WsZjdeEBZXbMidm6ipF23ct@public.gmane.org>
2007-12-07 20:06 ` J. Bruce Fields
2007-12-07 20:00 ` Erez Zadok
2007-12-07 20:05 ` Erez Zadok
2007-12-07 20:05 ` Erez Zadok
2007-12-07 2:20 Erez Zadok
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=20071207153230.GA20872@fieldses.org \
--to=bfields@fieldses.org \
--cc=ezk-EX0cT3Az47bauI2f2gSDlQ@public.gmane.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe-1zs4UD6AkMk@public.gmane.org \
--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.