From: Suresh Jayaraman <sjayaraman@suse.de>
To: linux-nfs@vger.kernel.org
Subject: Better error/warning message while exporting ramfs
Date: Thu, 13 Dec 2007 18:22:56 +0530 [thread overview]
Message-ID: <47612B28.4040103@suse.de> (raw)
While trying to export non-device filesystems like tmpfs and ramfs,
nfs-utils version < 1.1.0 didn't report any error or warning message. So
the users were left clueless by the "Permission denied" message on the
Client, though it was possible to export tmpfs by setting
'fsid=<somenum>' option.
nfs-utils 1.1.0 and greater reported a much better warning:
"exportfs: Warning: /mnt/js requires fsid= for NFS export"
However, this warning message is reported only while exporting tmpfs and
not while exporting ramfs.
#mount -t ramfs ramfs /mnt/js
#exportfs -v -o rw,sync,no_subtree_check localhost:/mnt/js
exporting localhost:/mnt/js
exportfs: Warning: /mnt/js does not support NFS export.."
I think this is because trail export '-test-client-' with fsid 1 fails
in case of ramfs. Iam not sure about the differences between ramfs and
tmpfs but, "df -h" lists the tmpfs mounts while listing ramfs one. Not
sure whether this has something to do with this behaviour.
It would help if we report the same warning message while exporting
ramfs also.
Also, http://nfs.sourceforge.net/#faq_c6 needs an update?
Thanks,
--
Suresh Jayaraman
reply other threads:[~2007-12-13 12:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47612B28.4040103@suse.de \
--to=sjayaraman@suse.de \
--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