February 2025 - Devel - NFS Ganesha List Archives

[S] Change in ...nfs-ganesha[next]: Refcount log to track STATE_CLIENTID_OWNER_NFSV4 owner
by Xueqian Hu (GerritHub) 27 Feb '25

27 Feb '25

Xueqian Hu has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209466?usp=email ) Change subject: Refcount log to track STATE_CLIENTID_OWNER_NFSV4 owner ...................................................................... Refcount log to track STATE_CLIENTID_OWNER_NFSV4 owner Display caller of inc_state_owner_ref & dec_state_owner_ref to track refcount. Change-Id: I32882df7ff56e833f8cc5376189a015da9c3642b Signed-off-by: Xueqian Hu <xh140312(a)outlook.com> --- M src/SAL/state_misc.c M src/include/sal_functions.h 2 files changed, 22 insertions(+), 4 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/66/1209466/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209466?usp=email To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: I32882df7ff56e833f8cc5376189a015da9c3642b Gerrit-Change-Number: 1209466 Gerrit-PatchSet: 1 Gerrit-Owner: Xueqian Hu <xh140312(a)outlook.com>

1 0

[XS] Change in ...nfs-ganesha[next]: SAL: Mark completion of takeover correctly
by Sachin Punadikar (GerritHub) 27 Feb '25

27 Feb '25

Sachin Punadikar has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209463?usp=email ) Change subject: SAL: Mark completion of takeover correctly ...................................................................... SAL: Mark completion of takeover correctly Ganesha supports takeover (node or IP failover) functionality for "rados_cluster" backend. Need to mark the takeover activity completion when grace period is over. Change-Id: I91963ce52b721b221ef2c62194799a9bae412b28 Signed-off-by: Sachin Punadikar <sachin.punadikar(a)ibm.com> --- M src/SAL/recovery/recovery_rados_cluster.c 1 file changed, 3 insertions(+), 1 deletion(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/63/1209463/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209463?usp=email To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: I91963ce52b721b221ef2c62194799a9bae412b28 Gerrit-Change-Number: 1209463 Gerrit-PatchSet: 1 Gerrit-Owner: Sachin Punadikar <sachin.punadikar(a)ibm.com>

1 0

[S] Change in ...nfs-ganesha[next]: FSAL_VFS: Lock reclaim not working on NFSv4.1 due to locks not being ...
by Peter Schwenke (GerritHub) 26 Feb '25

26 Feb '25

Peter Schwenke has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209432?usp=email ) Change subject: FSAL_VFS: Lock reclaim not working on NFSv4.1 due to locks not being released ...................................................................... FSAL_VFS: Lock reclaim not working on NFSv4.1 due to locks not being released Fixes: https://github.com/nfs-ganesha/nfs-ganesha/issues/1237 In the case of NFSv4.1, the Linux NFS client doesn't send an IP address in the eia_clientowner field during the OP_EXCHANGE_ID op. NFS-Ganesha pulls the address out of the socket information and puts it in cr_server_addr. In 4.0 cr_server_addr is 0. But the OP_SETCLIENTID op sends an IP address in id_val. Change-Id: I59d4e895a40b060b8477f8daf900a5ddaa5da1c1 Signed-off-by: Peter Schwenke <pschwenke(a)ddn.com> --- M src/SAL/nfs4_recovery.c 1 file changed, 38 insertions(+), 4 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/32/1209432/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209432?usp=email To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: I59d4e895a40b060b8477f8daf900a5ddaa5da1c1 Gerrit-Change-Number: 1209432 Gerrit-PatchSet: 1 Gerrit-Owner: Peter Schwenke <pschwenke(a)ddn.com>

1 0

[XS] Change in ...nfs-ganesha[next]: NFS Ganesha crashes with SEGV on Startup
by Peter Schwenke (GerritHub) 26 Feb '25

26 Feb '25

Peter Schwenke has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209430?usp=email ) Change subject: NFS Ganesha crashes with SEGV on Startup ...................................................................... NFS Ganesha crashes with SEGV on Startup Fixes: https://github.com/nfs-ganesha/nfs-ganesha/issues/1236 Allow -I option to take an argument. The colon disappeared when the -V option was added in commit 7c726fbfbb. Change-Id: I8f86e1bcf41744f7259830101a7fb2512680f2e4 Signed-off-by: Peter Schwenke <pschwenke(a)ddn.com> --- M src/MainNFSD/nfs_main.c 1 file changed, 1 insertion(+), 1 deletion(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/30/1209430/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209430?usp=email To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: I8f86e1bcf41744f7259830101a7fb2512680f2e4 Gerrit-Change-Number: 1209430 Gerrit-PatchSet: 1 Gerrit-Owner: Peter Schwenke <pschwenke(a)ddn.com>

1 0

nfstest_pnfs - read_write test suite failing with NFS ganesha (Gluster FS)
by meenu2sachan＠gmail.com 24 Feb '25

24 Feb '25

I have a 4 Node Gluster setup (Redhat 7), deployed NFS ganesha (V7-dev.4-0-g8ae799) on all node with 1 MDS & 3 DS. I am running nfstest_pnfs test suite which do basic compliance test (https://wiki.linux-nfs.org/wiki/index.php/NFStest) For read_write tests it performs 3 stages 1. Verify traffic for file using pNFS - READ 2. Verify traffic for second file using pNFS within the same mount - READ 3. Verify traffic for first file opened again using pNFS within the same mount - WRITE During stage 3 test expects below things which are getting failed. 1. LAYOUTGET stateid should be the previous LAYOUTGET stateid 2. GETDEVICEINFO should not be sent for the same file 3. EXCHANGE_ID should not be sent to DS(0) 4. CREATE_SESSION should not be sent to DS(0) 5. RECLAIM_COMPLETE should not be sent to DS(0) 6. LAYOUTRETURN should be sent to MDS, 1 call missing 7. LAYOUTRETURN should use the layout stateid 8. DESTROY_SESSION should be sent to DS(0) on umount Form packet capture we could see the sequence of events … For failure 1-5 Test Create/Open file test_pnfs_*_f_004 and does a get layout ---> Server returns Device ID 1 (lets assume 1), test1 runs bunch of tests and completes it and does a layout return and destroy session and destroy client ID. Test → Open same file test_pnfs_*_f_004 and does a get layout ---> Server returns Device ID 2 ---> This is making the nfstest_pnfs upset. For failure 6-8 Test1 completes the test and does a close session ID and as part of close session id it is also sending layout return and destroy session. Test2 completes the test and does a close session ID and as part of close session id here also it is sending layout return and destroy session. Now Test3 when it completes the tests it is expecting 3 LAYOUT RETURN while test1 and test2 have already sent. Did any one observed this behaviour? If yes, how to resolve same?

2 1

Updated invitation: Ganesha community call @ Tue Mar 25, 2025 4pm - 5pm (GMT+2) (devel@lists.nfs-ganesha.org)
by Galia Eldar 24 Feb '25

24 Feb '25

This event has been updated Changed: location Ganesha community call Tuesday Mar 25, 2025 ⋅ 4pm – 5pm Israel Time Location IL-TLV-ELCO-43-0-KitKat (16) [GVC] https://www.google.com/maps/search/IL-TLV-ELCO-43-0-KitKat+(16)+%5BGVC%5D?h… Join with Google Meet https://meet.google.com/mkh-ctnj-tqz?hs=224 Join by phone (US) +1 401-702-0462 PIN: 495972631 More joining options https://tel.meet/mkh-ctnj-tqz?pin=2844708468265&hs=0 Join using SIP 2844708468265(a)gmeet.redhat.com ID: 2844708468265 Organizer ffilz(a)redhat.com ffilz(a)redhat.com Guests ffilz(a)redhat.com - organizer thomas.vanderputten(a)panzura.com ffilzg(a)gmail.com dgryniew(a)redhat.com dmanzoni(a)verisign.com martin(a)uni-mainz.de mbenjami(a)redhat.com kkeithle(a)redhat.com Bjorn Leffler sagar.it.iiests(a)gmail.com geva30(a)gmail.com Assaf Yaari Lior Suliman Gaurav Sharma Yash Narang Dipit Grover Roop Tyagi alok(a)spillbox.io punadikar.sachin(a)gmail.com ndevos(a)ibm.com sriram.patil(a)broadcom.com itsmerojin(a)gmail.com David Rieber Yoni Couriel Shahar Hochma nchillar(a)redhat.com Ofir Vainshtein Miki Ivry ajavali(a)redhat.com arateria(a)redhat.com deepatil(a)redhat.com raprasad(a)redhat.com sathani(a)redhat.com shivsing(a)redhat.com vthumuku(a)redhat.com Roy Babayov Idan Eldar Marc Eshel RICHARD RUPP devel(a)lists.nfs-ganesha.org Wyll Ingersoll hu hansen ffilz(a)ibm.com Marcus Gorzellik Yogendra Charya Sriram Patil Jacobson, Erik blaine.gardner(a)ibm.com naresh.chillarege(a)ibm.com animesh.javali(a)ibm.com Rajesh Prasad Nishant Puri sreedhar.agraharam(a)ibm.com View all guest info https://calendar.google.com/calendar/event?action=VIEW&eid=NXZubmZhbGJwcTdi… Reply for devel(a)lists.nfs-ganesha.org and view more details https://calendar.google.com/calendar/event?action=VIEW&eid=NXZubmZhbGJwcTdi… Your attendance is optional. ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 0

[XL] Change in ...nfs-ganesha[next]: QOS Implementation.
by Name of user not set (GerritHub) 20 Feb '25

20 Feb '25

deeraj.patil(a)ibm.com has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209096?usp=email ) Change subject: QOS Implementation. ...................................................................... QOS Implementation. 1. IO bandwidth control (Data, Bytes Per Second). 2. IOPS (IO Operation Per Second). 2. Quota (N/W data Limit over a larger time). Bandwidth Control: Two types of approaches are there for bandwidth control: SYNC and ASYNC. Sync Control : Per-Share, Per-Client. (macro in code currently disabled) ASYNC Control : Per-Share, Per-Client, PerShare-PerClient Combined. Default ASYNC macro is enabled in code (!BW_SYNC_ENABLE). Default ASYNC type is PerShare-PerClient. IOPS Control: Only ASYNC IOPS Control is supported. Can be enabled at : Per-Share, Per-Client, PerShare-PerClient. Default type is PerShare-PerClient(Combined Only). Quota Control: i.e (Network Data Consumtion limit over a period of larger time). Per-Share level, Per-Client level, or can PerShare-PerClient level. Default : Quota is currently disabled. Can indvidually enable BW control, IOPS Control, Quota. Limit values for Bandwidth and Quota can be controlled indvidually for Write and Read or can be combined together. For IOPS only Combined accounting supported (can be extended in future). For enabling QOS, enable_qos params should be true in global config. Default value for enable_qos in global config is false. For Controlling ratelimiting values dynamically : 1.DBUS interface (Currently only for BW control). 2.Dynamic config update at export level(Using SIGHUP). QOS CompileTime enable and disablement, using ENABLE_QOS flag while doing CMAKE. Implemented by naresh.chillarege(a)ibm.com and deeraj.patil(a)ibm.com Change-Id: I36f064ef91ba3ba2ef6fd0fcb3d490a8ff114757 Signed-off-by: Deeraj.Patil <Deeraj.Patil(a)ibm.com> --- M src/CMakeLists.txt M src/MainNFSD/CMakeLists.txt M src/MainNFSD/nfs_init.c A src/MainNFSD/nfs_qos.c M src/Protocols/NFS/nfs4_Compound.c M src/Protocols/NFS/nfs4_op_destroy_session.c M src/Protocols/NFS/nfs4_op_read.c M src/Protocols/NFS/nfs4_op_write.c M src/include/client_mgr.h M src/include/config-h.in.cmake M src/include/export_mgr.h M src/include/log_common.h M src/include/nfs_proto_data.h A src/include/nfs_qos.h A src/include/nfs_qosmgr.h M src/log/log_functions.c M src/support/client_mgr.c M src/support/exports.c A src/support/nfs_qosmgr.c M src/support/nfs_read_conf.c 20 files changed, 5,417 insertions(+), 9 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/96/1209096/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209096?usp=email To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: I36f064ef91ba3ba2ef6fd0fcb3d490a8ff114757 Gerrit-Change-Number: 1209096 Gerrit-PatchSet: 1 Gerrit-Owner: deeraj.patil(a)ibm.com

1 0

[M] Change in ...nfs-ganesha[next]: fix(readdir): encode "next entry" flag in readdir reply
by Zhitao Li (GerritHub) 20 Feb '25

20 Feb '25

Zhitao Li has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209069?usp=email ) Change subject: fix(readdir): encode "next entry" flag in readdir reply ...................................................................... fix(readdir): encode "next entry" flag in readdir reply This commit resolves the issue described in #1234. When FSAL readdir completes without hitting both EOF of the directory and DIR_TERMINATE in the readdir callback, the "next entry" flag is missing in the reply. This causes the Windows NFS client to misinterpret the directory as empty in File Explorer, while the Linux NFS client handles it correctly. The fix ensures that the "next entry" flag is included in the readdir reply in this scenario, allowing Windows clients to correctly display the directory contents. Change-Id: I594b03073d9023d1d05ab889f9fbd1a577b603fa Signed-off-by: zhitaoli <zhitao.li(a)iomesh.com> --- M src/Protocols/NFS/nfs3_readdir.c M src/Protocols/NFS/nfs3_readdirplus.c M src/Protocols/NFS/nfs4_op_readdir.c 3 files changed, 42 insertions(+), 63 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/69/1209069/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209069?usp=email To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: I594b03073d9023d1d05ab889f9fbd1a577b603fa Gerrit-Change-Number: 1209069 Gerrit-PatchSet: 1 Gerrit-Owner: Zhitao Li <zhitao.li(a)iomesh.com>

1 0

[S] Change in ...nfs-ganesha[next]: Ceph : Correct the reclaim_reset logic
by Sachin Punadikar (GerritHub) 19 Feb '25

19 Feb '25

Sachin Punadikar has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209026?usp=email ) Change subject: Ceph : Correct the reclaim_reset logic ...................................................................... Ceph : Correct the reclaim_reset logic In case of Ganesha failure, once Ganesha comes back, the associated ceph client has to reclaim its old status/CAPS. For identifying the ceph client, an uuid string is formed using first exportid. This will lead to reclaim failure when one removes the first export. Instead of relying on exportid, defaulting it to make use of 0001 in the uuid string. Also propagting back the ceph side failure (as applicable) to Ganesha, instead of hiding it. Change-Id: I978138f1d12399e7e23c5f46e424ccc5363f44bd Signed-off-by: Sachin Punadikar <sachin.punadikar(a)ibm.com> --- M src/FSAL/FSAL_CEPH/main.c 1 file changed, 15 insertions(+), 8 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/26/1209026/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209026?usp=email To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: I978138f1d12399e7e23c5f46e424ccc5363f44bd Gerrit-Change-Number: 1209026 Gerrit-PatchSet: 1 Gerrit-Owner: Sachin Punadikar <sachin.punadikar(a)ibm.com>

1 0

[XS] Change in ...nfs-ganesha[next]: Doc : Correct documentation of "nodeid"
by Sachin Punadikar (GerritHub) 18 Feb '25

18 Feb '25

Sachin Punadikar has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209006?usp=email ) Change subject: Doc : Correct documentation of "nodeid" ...................................................................... Doc : Correct documentation of "nodeid" Change-Id: Ic42ac0c7abed297242a4a7d9a2eb4bdbc3ff6f11 Signed-off-by: Sachin Punadikar <sachin.punadikar(a)ibm.com> --- M src/doc/man/ganesha-core-config.rst 1 file changed, 5 insertions(+), 2 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/06/1209006/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1209006?usp=email To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: Ic42ac0c7abed297242a4a7d9a2eb4bdbc3ff6f11 Gerrit-Change-Number: 1209006 Gerrit-PatchSet: 1 Gerrit-Owner: Sachin Punadikar <sachin.punadikar(a)ibm.com>

1 0