From: "J. Bruce Fields" <bfields@fieldses.org>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: nfs-utils crossmnt/fsid bug
Date: Wed, 5 Sep 2007 16:46:28 -0400 [thread overview]
Message-ID: <20070905204628.GD29582@fieldses.org> (raw)
With an exports entry like
/exports *.citi.umich.edu(rw,crossmnt,fsid=0)
and some other stuff mounted under /exports, I get an odd situation
where listing /exports/submnt/ shows me the contents of /exports/.
I looks to me like what's happening is that the new code to
automatically export filesystems under crossmnt exports is exporting
those directories with the fsid option turned on, with the result that
the root of each of those subdirectories ends up with the same
filehandle as the root of /exports, and the hilarity ensues. But I
haven't tried a patch yet.
Does that make sense? I assume we should just clear the fsid flag on
submounts, as it's never going to make sense, and leave the logic
otherwise intact.
--b.
-------------------------------------------------------------------------
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 reply other threads:[~2007-09-05 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 20:46 J. Bruce Fields [this message]
2007-11-23 2:50 ` [NFS] nfs-utils crossmnt/fsid bug Neil Brown
[not found] ` <18246.16373.177320.570040-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2007-11-26 22:39 ` J. Bruce Fields
2007-11-29 3:59 ` Neil Brown
2007-12-03 22:51 ` Frank Filz
2007-12-04 1:09 ` Neil Brown
[not found] ` <18260.43206.943331.889058-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2007-12-04 17:42 ` Frank Filz
2007-12-07 19:05 ` Frank Filz
2007-12-11 21:20 ` Frank Filz
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=20070905204628.GD29582@fieldses.org \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.