Bug 170097
| Summary: | NFS server exporting wrong filesystem | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Mikael M. Hansen <mhansen> |
| Component: | nfs-utils | Assignee: | Steve Dickson <steved> |
| Status: | CLOSED NOTABUG | QA Contact: | Ben Levenson <benl> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-12-21 13:37:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Any help on this? What has changed since RHEL3? Everything... :-\ Try adding the 'no_subtree_check' and 'nohide' export options to see how it effect things... did the no_subtree_check and/or nohide export options help? Nope. We still get the underlying file system. from time to time. But as we have changed most of the software to mount directly from the server using its own mount point I really cannot tell if the problem is still there. Just close it. |
Description of problem: We experience once in a while that we mount the wrong filesystem from our fileservers using /n. We get a directory on the / filesystem and not a directory on the /q/lfs0_11 filesystem as expected. To be precise we do a: cd /n/file.host.name.here/q/lfs0_11 ls Sometimes we get the contents of the /q/lfs0_11 filesystem and sometimes we get nothing (the contents of /q/lfs0_11 directory under the / filesystem). The details: The fileserver now runs RHEL4 The client runs Solaris9 or RHEL3 (possibly also RHEL4, could not get it to error while writing this bugreport, but have received reports from users that is also fails.) We ran RHEL3 on the server before the summer and had no problems, so it is somehow related to the upgrade from RHEL3 to RHEL4 on the servers. /etc/exports on the server: @adm(rw,no_root_squash,insecure,sync) /var @adm(rw,no_root_squash,insecure,sync) /tmp @adm(rw,no_root_squash,insecure,sync) /q/disk_0 @nadm(rw,insecure,sync) @adm(rw,no_root_squash,insecure,sync) /q/disk_1 @nadm(rw,insecure,sync) @adm(rw,no_root_squash,insecure,sync) /q/lfs0_0 @nadm(rw,insecure,sync) @adm(rw,no_root_squash,insecure,sync) /q/lfs0_1 @nadm(rw,insecure,sync) @adm(rw,no_root_squash,insecure,sync) More entries similar to above (except number in the end) has been removed. We naturally get no errors in /var/log/messages on the servers. Any suggestions on what to do. What has changed between RHEL3 and RHEL4 that can trigger this behaviour? Version-Release number of selected component (if applicable): nfs-utils-1.0.6-46 How reproducible: Sometimes, but not always Steps to Reproduce: 1. cd /n/file.host.name.here/q/lfs0_11 2. ls 3. continue by doing 1. again but exchange lfs0_11 with lfs0_10 etc. until ls gives an empty result Actual results: Expected results: Additional info: