From: Jeff Layton <jlayton@redhat.com>
To: "Muntz, Daniel" <Dan.Muntz@netapp.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Neil Brown <neilb@suse.de>,
nfs@lists.sourceforge.net
Subject: Re: Exportfs not showing exported file systems (was RE: stdio and nfs-utils)
Date: Thu, 26 Jul 2007 15:48:06 -0400 [thread overview]
Message-ID: <20070726154806.ed0afdfd.jlayton@redhat.com> (raw)
In-Reply-To: <01AE8AF878612047A442668306EAEB05D02161@SACEXMV01.hq.netapp.com>
On Thu, 26 Jul 2007 11:43:10 -0700
"Muntz, Daniel" <Dan.Muntz@netapp.com> wrote:
> Could all this be related to a problem that we've been seeing while
> working on v4/4.1 at netapp, where exportfs doesn't show any output even
> when there are exported file systems? Ricardo recently observed that if
> you redirect the output of 'exportfs' then you actually do get the
> correct output (e.g., exportfs > afile, or exportfs | more). This lead
> to some experiments with strace that show exportfs behaving differently
> when its output is going to a tty. We've seen this behavior across a
> variety of kernels (2.6.18-2.6.20) and a variety of nfs-utils
> (prepackaged with FC6, RHEL4/5, and built from a local copy of 1.0.12).
>
I saw a very similar problem with RHEL5 prior to its release. It turned
out to be a selinux policy issue. I believe the latest selinux-policy
packages in Fedora and RHEL have fixed it if it's the same problem.
--
Jeff Layton <jlayton@redhat.com>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-07-26 19:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 22:37 stdio and nfs-utils J. Bruce Fields
2007-07-26 0:07 ` J. Bruce Fields
2007-07-26 2:59 ` Neil Brown
2007-07-26 3:17 ` J. Bruce Fields
2007-07-26 4:10 ` Neil Brown
2007-07-26 20:30 ` [PATCH] Use __fpurge to ensure single-line writes to cache files J. Bruce Fields
2007-07-26 20:31 ` [PATCH] knfsd: eliminate unnecessary -ENOENT returns on export downcalls J. Bruce Fields
2007-07-26 18:43 ` Exportfs not showing exported file systems (was RE: stdio and nfs-utils) Muntz, Daniel
2007-07-26 19:36 ` J. Bruce Fields
2007-07-26 19:48 ` Jeff Layton [this message]
2007-07-26 20:04 ` J. Bruce Fields
2007-07-26 20:42 ` Muntz, Daniel
2007-07-26 21:12 ` Jeff Layton
2007-07-26 21:16 ` J. Bruce Fields
2007-07-26 21:40 ` Muntz, Daniel
2007-07-27 14:40 ` Steve Dickson
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=20070726154806.ed0afdfd.jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=Dan.Muntz@netapp.com \
--cc=bfields@fieldses.org \
--cc=neilb@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox