Bug 428486 - Unable to navigate to loop-mounted directories within an export.
Summary: Unable to navigate to loop-mounted directories within an export.
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: nfs-utils
Version: 4.6
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: yanfu,wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-12 00:59 UTC by Ray Van Dolson
Modified: 2011-12-08 15:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-08 15:35:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ray Van Dolson 2008-01-12 00:59:10 UTC
Description of problem:
Say I have a directory /export:

/export
  /disc1
  /disc2

Where /disc1 and disc2 have been mounted as such:

mount -o loop,ro /root/disc1.iso /export/disc1
mount -o loop,ro /root/disc1.iso /export/disc1

And /export is exported as such:

/export   *(ro,sync,no_subtree_check,no_root_squash)

When a client mounts this directory:

# mount -t nfs host:/export /mnt
# cd /mnt
# ls -l

This operation takes a long time and eventually returns a directory listing. 
However, upon cd'ing to one of the subdirectories disc1 or disc2 these
directories show no contents.

It appears the only way is to explicitly export each directory (/export/disc1,
/export/disc2) separately.

This appears to be a bug:

  http://marc.info/?l=linux-nfs&m=119389121928817&w=2

Fixed here in 1.1.1-git:

 
http://git.linux-nfs.org/?p=steved/nfs-utils-exp.git;a=commitdiff;h=bfdc26916d8dabd319240a3ce5198b6189040be7

Questions:

  - Am I correct in stating that this is a bug?
  - Is the above mentioned fix feasible for backport to nfs-utils 1.0.6 in
RHEL4?  If so, I can open an SR to request having this done.

This issue also exists in RHEL5 (nfs-utils 1.0.9).  May open a separate bug for
that as well.


Note You need to log in before you can comment on or make changes to this bug.