From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Paweł Sikora" <pawel.sikora@agmk.net>
Cc: Steve Dickson <SteveD@redhat.com>,
linux-nfs@vger.kernel.org, baggins@pld-linux.org,
Trond.Myklebust@netapp.com
Subject: Re: mount.nfs: cannot allocate memory.
Date: Wed, 16 Jan 2013 15:15:10 -0500 [thread overview]
Message-ID: <20130116201510.GA6598@fieldses.org> (raw)
In-Reply-To: <2365095.7zaHsQeZKG@localhost>
On Wed, Jan 16, 2013 at 09:07:45PM +0100, Paweł Sikora wrote:
> On Wednesday 16 of January 2013 14:39:32 J. Bruce Fields wrote:
> > On Wed, Jan 16, 2013 at 08:03:14PM +0100, Paweł Sikora wrote:
> > > [259176.973751] NFS: nfs mount opts='soft,addr=10.0.2.28,vers=3,proto=tcp,mountvers=3,mountproto=udp,mountport=50252'
> > > [259176.973757] NFS: parsing nfs mount option 'soft'
> > > [259176.973759] NFS: parsing nfs mount option 'addr=10.0.2.28'
> > > [259176.973765] NFS: parsing nfs mount option 'vers=3'
> > > [259176.973769] NFS: parsing nfs mount option 'proto=tcp'
> > > [259176.973772] NFS: parsing nfs mount option 'mountvers=3'
> > > [259176.973776] NFS: parsing nfs mount option 'mountproto=udp'
> > > [259176.973779] NFS: parsing nfs mount option 'mountport=50252'
> > > [259176.973784] NFS: MNTPATH: '/R10'
> > > [259176.973788] NFS: sending MNT request for nexus:/R10
> > > [259176.974620] NFS: received 1 auth flavors
> > > [259176.974623] NFS: auth flavor[0]: 1
> > > [259176.974640] NFS: MNT request succeeded
> > > [259176.974643] NFS: using auth flavor 1
> > > [259176.974688] --> nfs_init_server()
> > > [259176.974691] --> nfs_get_client(nexus,v3)
> > > [259176.974698] NFS: get client cookie (0xffff88021146f800/0xffff8800ceb06640)
> > > [259176.975704] <-- nfs_init_server() = 0 [new ffff88021146f800]
> > > [259176.975708] --> nfs_probe_fsinfo()
> > > [259176.975711] NFS call fsinfo
> > > [259176.975959] NFS reply fsinfo: -116
> >
> > That's ESTALE. Might be interesting to see the network traffic between
> > client and server.
>
> here's the tcpdump result: http://pluto.agmk.net/kernel/nfs.mount.estale.dump
On just a very quick skim (you may want to verify to see I've got it
right), frame 30 shows the server returning a filehandle in a MNT reply,
then frame 48 shows the same client that got that MNT reply using the
same filehandle in an FSINFO reply, and getting an NFS3ERR_STALE
response.
Offhand seems like a server bug. Might conceivably happen if there was
some confusion whether the client was authorized to access that export?
--b.
next prev parent reply other threads:[~2013-01-16 20:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 9:27 mount.nfs: cannot allocate memory Paweł Sikora
2013-01-03 14:42 ` Steve Dickson
2013-01-04 5:16 ` Paweł Sikora
2013-01-04 6:03 ` fanchaoting
2013-01-04 15:20 ` Paweł Sikora
2013-01-05 10:08 ` Paweł Sikora
2013-01-07 14:47 ` Steve Dickson
2013-01-09 17:44 ` Paweł Sikora
2013-01-16 19:03 ` Paweł Sikora
2013-01-16 19:39 ` J. Bruce Fields
2013-01-16 20:07 ` Paweł Sikora
2013-01-16 20:15 ` J. Bruce Fields [this message]
2013-01-16 21:18 ` Paweł Sikora
2013-01-17 13:49 ` J. Bruce Fields
2013-01-17 14:59 ` Paweł Sikora
2013-01-16 20:14 ` Myklebust, Trond
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=20130116201510.GA6598@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=baggins@pld-linux.org \
--cc=linux-nfs@vger.kernel.org \
--cc=pawel.sikora@agmk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).