This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2177263 - df: duplicates listed bind mounts for remote filesystems (NFS) with same fsid/device without "-a", even with BZ 1962515 fixed.
Summary: df: duplicates listed bind mounts for remote filesystems (NFS) with same fsid...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: coreutils
Version: 8.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Lukáš Zaoral
QA Contact: Radka Brychtova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-10 16:10 UTC by Ayan Neogi
Modified: 2023-09-20 19:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-20 19:33:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-5649 0 None Migrated None 2023-09-20 19:33:35 UTC
Red Hat Issue Tracker RHELPLAN-151451 0 None None None 2023-03-10 16:10:58 UTC

Description Ayan Neogi 2023-03-10 16:10:14 UTC 
Description of problem:

I get duplicates on this reproducer even with BZ 1962515 fixed,
i.e. without -a, duplicates are listed for remote FS/s under 
same device (same exported fsid), when it is bind mounted, test case for NFS:

## RHEL8:

$ uname -r
4.18.0-425.13.1.el8_7.x86_64

$ rpm -q coreutils
coreutils-8.30-13.el8.x86_64

$ mkdir -p /original /bind1 /bind2

$ mount.nfs server:/nfs /original -v     
mount.nfs: timeout set for Fri Mar 10 10:50:59 2023
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.122.40,clientaddr=192.168.122.121'

$ mount --bind /original/testd1 /bind1 -v
mount: /original/testd1 bound on /bind1.

$ mount --bind /original/testd2 /bind2 -v
mount: /original/testd2 bound on /bind2.

$ df -ht nfs4                            
Filesystem          Size  Used Avail Use% Mounted on
server:/nfs          97M  5.4M   92M   6% /original
server:/nfs/testd1   97M  5.4M   92M   6% /bind1   
server:/nfs/testd2   97M  5.4M   92M   6% /bind2   

$ mount --bind /original/testd1 /bind1 -v
mount: /original/testd1 bound on /bind1.

$ mount --bind /original/testd2 /bind2 -v
mount: /original/testd2 bound on /bind2.

$ df -ht nfs4
Filesystem          Size  Used Avail Use% Mounted on
server:/nfs          97M  5.4M   92M   6% /original
server:/nfs/testd1   97M  5.4M   92M   6% /bind1   
server:/nfs/testd2   97M  5.4M   92M   6% /bind2   
server:/nfs/testd1   97M  5.4M   92M   6% /bind1   <--- dup
server:/nfs/testd2   97M  5.4M   92M   6% /bind2   <--- dup

$ cat /proc/fs/nfsfs/volumes 
NV SERVER   PORT DEV          FSID                              FSC
v4 c0a87a28  801 0:55         8d133867f8e04cf9:984d43c5f2b82b17 no 

$ grep 0:55 /proc/self/mountinfo
423 97 0:55 / /original rw,relatime shared:219 - nfs4 ...
421 97 0:55 / /bind1 rw,relatime shared:219 - nfs4 ...
439 97 0:55 / /bind2 rw,relatime shared:219 - nfs4 ...
449 421 0:55 / /bind1 rw,relatime shared:219 - nfs4 ...
459 423 0:55 / /original/testd1 rw,relatime shared:219 - nfs4 ...
502 439 0:55 / /bind2 rw,relatime shared:219 - nfs4 ...
503 423 0:55 / /original/testd2 rw,relatime shared:219 - nfs4 ...


Version-Release number of selected component (if applicable): 8.7, coreutils-8.30-13.el8.x86_64


How reproducible: 100%


Steps to Reproduce: see above
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Kamil Dudka 2023-03-21 16:44:12 UTC 
Thank you for reporting it!  I am able to reproduce the described behavior.  I do not think it is the same issue that bug #1962515 was supposed to fix though.  Bug #1962515 was fixing a regression introduced by the following upstream commit:

    https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v8.25-54-g1c17f61ef99

... whereas the behavior described in this bug seems to be consistent from RHEL-7 through Fedora.
Comment 2 RHEL Program Management 2023-09-20 19:31:56 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 3 RHEL Program Management 2023-09-20 19:33:38 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.