Bug 1931343 - [rhel8] On UDP mount with NFS v3 'ls' stuck on mountpoint
Summary: [rhel8] On UDP mount with NFS v3 'ls' stuck on mountpoint
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: nfs-ganesha
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: RHGS 3.5.z Batch Update 7
Assignee: Daniel Gryniewicz
QA Contact: Sri Vignesh Selvan
URL:
Whiteboard:
Depends On:
Blocks: 1975399
TreeView+ depends on / blocked
 
Reported: 2021-02-22 08:46 UTC by Upasana
Modified: 2023-09-15 01:01 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, NFSv3 user datagram protocol (UDP) readdir replies were not properly formatted and never sent. Hence, the directory listings on the client would fail. With this update, the replies are correctly formatted for NFSv3 on UDP and the directory listings on the client are successful.
Clone Of:
: 1975399 (view as bug list)
Environment:
Last Closed: 2021-10-05 07:57:33 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:3727 0 None None None 2021-10-05 07:57:47 UTC

Description Upasana 2021-02-22 08:46:41 UTC
Description of problem:
=======================
While trying to verify 'https://bugzilla.redhat.com/show_bug.cgi?id=1843921'
and mounting the volume on UDP,NFSv3 , the mount-point goes to a hung state on issuing lookup via 'ls'

Version-Release number of selected component (if applicable):
=============================================================
glusterfs-6.0-52.el8rhgs.x86_64


How reproducible:
=================
2/2
Both on RHEL-7 & RHEL-8


Steps to Reproduce:
===================
1.Create a volume and enable ganesha
2.Mount the volume via UDP using NFSv3 (mount successful)
3.Do a lookup on the mountpoint - ls is stuck

Actual results:
===============
Lookup(ls) is on a hung state

Expected results:
=================
Lookup should pass successfully

Additional info:
================
[root@dhcp46-106 ~]# gluster v info ganesha
 
Volume Name: ganesha
Type: Distributed-Replicate
Volume ID: 7f5d15ad-6329-4b9f-bff8-a5b82f4b02d8
Status: Started
Snapshot Count: 0
Number of Bricks: 4 x 3 = 12
Transport-type: tcp
Bricks:
Brick1: 10.70.46.106:/gluster/brick1/b1
Brick2: 10.70.47.117:/gluster/brick1/b1
Brick3: 10.70.46.118:/gluster/brick1/b1
Brick4: 10.70.46.187:/gluster/brick1/b1
Brick5: 10.70.46.106:/gluster/brick2/b1
Brick6: 10.70.47.117:/gluster/brick2/b1
Brick7: 10.70.46.118:/gluster/brick2/b1
Brick8: 10.70.46.187:/gluster/brick2/b1
Brick9: 10.70.46.106:/gluster/brick3/b1
Brick10: 10.70.47.117:/gluster/brick3/b1
Brick11: 10.70.46.118:/gluster/brick3/b1
Brick12: 10.70.46.187:/gluster/brick3/b1
Options Reconfigured:
ganesha.enable: on
features.cache-invalidation: on
cluster.granular-entry-heal: on
storage.fips-mode-rchecksum: on
transport.address-family: inet
nfs.disable: on
performance.client-io-threads: off
nfs-ganesha: enable
cluster.enable-shared-storage: enable


[root@dhcp46-106 ~]# gluster v status ganesha
Status of volume: ganesha
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick 10.70.46.106:/gluster/brick1/b1       49155     0          Y       139594
Brick 10.70.47.117:/gluster/brick1/b1       49155     0          Y       134481
Brick 10.70.46.118:/gluster/brick1/b1       49155     0          Y       129657
Brick 10.70.46.187:/gluster/brick1/b1       49155     0          Y       88128
Brick 10.70.46.106:/gluster/brick2/b1       49156     0          Y       139610
Brick 10.70.47.117:/gluster/brick2/b1       49156     0          Y       134497
Brick 10.70.46.118:/gluster/brick2/b1       49156     0          Y       129673
Brick 10.70.46.187:/gluster/brick2/b1       49156     0          Y       88144
Brick 10.70.46.106:/gluster/brick3/b1       49157     0          Y       139626
Brick 10.70.47.117:/gluster/brick3/b1       49157     0          Y       134513
Brick 10.70.46.118:/gluster/brick3/b1       49157     0          Y       129689
Brick 10.70.46.187:/gluster/brick3/b1       49157     0          Y       88160
Self-heal Daemon on localhost               N/A       N/A        Y       146343
Self-heal Daemon on 10.70.46.187            N/A       N/A        Y       93306
Self-heal Daemon on 10.70.47.117            N/A       N/A        Y       139729
Self-heal Daemon on 10.70.46.118            N/A       N/A        Y       134858
 
Task Status of Volume ganesha
------------------------------------------------------------------------------
There are no active volume tasks
 
[root@dhcp46-106 ~]# rpm -qa|grep ganesha
nfs-ganesha-selinux-3.4-1.el8rhgs.noarch
glusterfs-ganesha-6.0-52.el8rhgs.x86_64
nfs-ganesha-gluster-3.4-1.el8rhgs.x86_64
nfs-ganesha-3.4-1.el8rhgs.x86_64

[root@dhcp46-106 ~]# rpm -qa|grep gluster
glusterfs-cli-6.0-52.el8rhgs.x86_64
glusterfs-geo-replication-6.0-52.el8rhgs.x86_64
glusterfs-server-6.0-52.el8rhgs.x86_64
glusterfs-selinux-1.0-2.el8rhgs.noarch
glusterfs-libs-6.0-52.el8rhgs.x86_64
glusterfs-client-xlators-6.0-52.el8rhgs.x86_64
glusterfs-ganesha-6.0-52.el8rhgs.x86_64
glusterfs-6.0-52.el8rhgs.x86_64
nfs-ganesha-gluster-3.4-1.el8rhgs.x86_64
glusterfs-fuse-6.0-52.el8rhgs.x86_64
glusterfs-api-6.0-52.el8rhgs.x86_64
python3-gluster-6.0-52.el8rhgs.x86_64
[root@dhcp46-106 ~]# 


Will add the server and client side (tcp) wireshark dump

Comment 17 errata-xmlrpc 2021-10-05 07:57:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (nfs-ganesha bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:3727

Comment 18 Red Hat Bugzilla 2023-09-15 01:01:48 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


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