Bug 1110624
Summary: | RHEL7 displays only one nfs mount in df output which are exported with "rw,nohide,crossmnt" | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jayashree <jayashree_doijad> |
Component: | coreutils | Assignee: | Ondrej Vasik <ovasik> |
Status: | CLOSED DUPLICATE | QA Contact: | qe-baseos-daemons |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.0 | CC: | cerninr, pbrady |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-11-05 16:23:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jayashree
2014-06-18 05:51:27 UTC
I can confirm the same, on RedHat Enterprise Linux 6.5. exported 2 Filesystems *(rw,sync,no_root_squash) and mount on RHEL-7 and only first mounted visible in the df -k output. I would like to redirect this to the coreutils... I can reproduce this problem creating to exports on the same file system on the server nfsserver# cat /etc/exports #/home *(rw,crossmnt,sec=sys:krb5:krb5i:krb5p) /home *(rw,nohide,crossmnt) /home/tmp *(rw,nohide,crossmnt) nfsclient#mount simhat:/home /mnt/home nfsclient#mount simhat:/home/tmp /mnt/home/tmp df -k just shows the first mount nfsserver:/home 20G 5.1G 14G 28% /mnt/home Both filesystems are in /proc/mounts and when I strace the df command (strace df -k) it does how the two file system getting stat()-ed stat("/mnt/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat("/mnt/home/tmp", {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0 So the df command does see them but its just not displaying them I would rather let coreutils people debug why df is not displaying the filesystem (since they know the command better). If it does turns out to be a NFS issue, just reassign this back to nfs-utils... *** This bug has been marked as a duplicate of bug 1100026 *** |