From: Tony Asleson <tasleson@redhat.com>
To: linux-nfs@vger.kernel.org
Subject: exportfs: Messages indicating unsupported operation that works
Date: Sun, 15 Dec 2013 21:19:07 -0600 [thread overview]
Message-ID: <52AE712B.3060404@redhat.com> (raw)
When I try to export a directory that has a space in it I get the following:
# exportfs *:"/mnt/has space"
exportfs: /mnt/has space does not support NFS export
exit code is 0.
If I do:
# exportfs -v
/mnt/has space <world>(ro,wdelay,root_squash,no_subtree_check,
sec=sys,ro,secure,root_squash,no_all_squash)
It exists and I can mount it from a client and everything appears fine.
I took a peek at the code and we are failing in test_export. We are
getting a -1 returned when we write to: /proc/net/rpc/nfsd.export/channel .
This seems like a confusing message when it appears that everything is
working, thoughts?
Notes:
- Kernel Linux rawhide 3.13.0-0.rc3.git1.2.fc21.x86_64
- nfs-utils: Latest from git, but this happens on older released
versions tested too.
Thanks,
Tony
next reply other threads:[~2013-12-16 3:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 3:19 Tony Asleson [this message]
2013-12-16 18:36 ` exportfs: Messages indicating unsupported operation that works J. Bruce Fields
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=52AE712B.3060404@redhat.com \
--to=tasleson@redhat.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).