linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "dE ." <de.techno@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: Cannot see contents of files over NFS share.
Date: Thu, 31 Jan 2013 00:53:24 +0530	[thread overview]
Message-ID: <5109732C.9080306@gmail.com> (raw)

I've shares with the following options in export --

anonuid=1000,anongid=1000,secure,no_subtree_check,ro,fsid=0,crossmnt

(Actually it doesn't matter. If I remove all the options except fsid 
(which's required for nfs4), it still doesn't work.)

I mount the shares with no options and over localhost.

ls works ok, so does cding to various directories and checking it's 
contents, but that's about it.

No program can read the contents of any file; all of them hang, but can 
be stopped by an interrupt signal.

--debug --syslog with rpc.nfsd gives nothing at all, just generic 
startup messages.

On the same machine, I can mount shares from other NFSv4 servers.

Please help!

             reply	other threads:[~2013-01-30 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 19:23 dE . [this message]
2013-01-30 20:20 ` Cannot see contents of files over NFS share J. Bruce Fields
2013-01-31  4:22   ` dE .
2013-01-31  5:53   ` dE .
2013-01-31 18:02   ` dE .

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=5109732C.9080306@gmail.com \
    --to=de.techno@gmail.com \
    --cc=linux-nfs@vger.kernel.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 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).