Bug 1243376 - FSAL_GLUSTER : cthon lock test failure for pnfs mount
Summary: FSAL_GLUSTER : cthon lock test failure for pnfs mount
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: nfs-ganesha
Classification: Retired
Component: FSAL_GLUSTER
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jiffin
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1243377
TreeView+ depends on / blocked
 
Reported: 2015-07-15 10:43 UTC by Jiffin
Modified: 2020-06-24 11:15 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
: 1243377 (view as bug list)
Environment:
Last Closed: 2020-06-24 11:15:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Jiffin 2015-07-15 10:43:20 UTC
Description of problem:
When cthon lock test run on pnfs mount it fails at the TEST no7

Test #7 - Test parent/child mutual exclusion.
	Parent: 7.0  - F_TLOCK [             ffc,               9] PASSED.
	Parent: Wrote 'aaaa eh' to testfile [ 4092, 7 ].
	Parent: Now free child to run, should block on lock.
	Parent: Check data in file to insure child blocked.
tlock: short read (got 0, expected 7)
	Child:  7.3  - F_LOCK  [             ffc,               9] PASSED.
	Child:  Write child's version of the data and release lock.

** PARENT pass 1 results: 22/22 pass, 0/0 warn, 0/0 fail (pass/total).

**  CHILD pass 1 results: 45/45 pass, 0/0 warn, 0/0 fail (pass/total).
lock tests failed


Version-Release number of selected component (if applicable):
mailine

How reproducible:
always

Steps to Reproduce:
1. create a volume
2. export the volume using nfs-ganesha
3. mount the volume using pnfs
4. Run cthon lock test on the mount


Actual results:
It is failing at testno7

Expected results:
It should pass successfully

Additional info:
It is not tested in normal nfs4.1 mount(may be issue exists in that too)

Comment 1 Kaleb KEITHLEY 2020-06-24 11:15:31 UTC
If this is still an issue please open an issue in the github tracker at https://github.com/nfs-ganesha/nfs-ganesha/issues


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