Bug 1243374

Summary:	FSAL_GLUSTER : iozone -a fails for pnfs mount
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Jiffin <jthottan>
Component:	nfs-ganesha	Assignee:	Jiffin <jthottan>
Status:	CLOSED CANTFIX	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	akhakhar, jthottan, kkeithle, ndevos, nlevinki, sankarshan, skoduri, smohan
Target Milestone:	---	Keywords:	TechPreview, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1243372	Environment:
Last Closed:	2018-11-15 05:00:27 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:
Bug Depends On:	1243372
Bug Blocks:

Description Jiffin 2015-07-15 10:36:18 UTC

+++ This bug was initially created as a clone of Bug #1243372 +++

Description of problem:

iozone -a fails for pnfs mount throwing read: Bad file descriptor error.

#iozone -a

	Auto Mode
	Command line used: iozone -a
	Output is in Kbytes/sec
	Time Resolution = 0.000001 seconds.
	Processor cache size set to 1024 Kbytes.
	Processor cache line size set to 32 bytes.
	File stride size set to 17 * record size.
                                                            random  random    bkwd   record   stride                                   
              KB  reclen   write rewrite    read    reread    read   write    read  rewrite     read   fwrite frewrite   fread  freread
              64       4  576282 1392258
Error reading block 0 66700000
read: Bad file descriptor


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

How reproducible:
almost (90%)

Steps to Reproduce:
1. Create a volume
2. Export via nfs-ganesha
3. Mount using pnfs(version = 4.1)
4. run iozone -a on the mount point

Actual results:
failed throwing bad file-descriptor error

Expected results:
should succeed

Additional info:
Only iozone -a (automated mode)fails

No crashes seen in bricks or nfs-ganesha

But when iozone run in individually (from test i = 0 to 8) all the test passes successfully.


It seems to be timing issue for performing the cache invalidation on the M.D.S

Comment 2 Kaleb KEITHLEY 2016-06-20 11:49:44 UTC

do we have a timeframe for pNFS coming out of tech preview?

Comment 7 Red Hat Bugzilla 2023-09-14 03:02:03 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days