Bug 1208819

Summary: mount ec volume through nfs, ls shows no file , but with specified filename, the file can be modified
Product: [Community] GlusterFS Reporter: zhoushicheng <madaozhou>
Component: disperseAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.6.2CC: bugs, gluster-bugs, jahernan, jiaowopan, madaozhou, mingfan.lu, ndevos, pkarampu, ravishankar, vbellur
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-13 12:05:53 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:

Description zhoushicheng 2015-04-03 09:57:35 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 zhoushicheng 2015-04-03 10:11:28 UTC
Description of problem:
ls cmd shows no file under mount point, but files can be create, modify, rename, open.
ls with file name show file info.

Version-Release number of selected component (if applicable):
gluster3.6.2
gluster3.6.3
nfsv3

How reproducible:


Steps to Reproduce:
1.Create ec volume.
2.Mount ec volume by nfs.
3.create new file and run ls cmd.

Actual results:
ls show 0 file

Expected results:
ls shows all the exiting file info.

Additional info:

Glusterfs3.6.1 has no such bug while mounting ec volume by nfs.
If mount the volume by fuse, all file could be listed by ls.

Comment 2 Frank Lu 2015-04-13 11:36:28 UTC
duplicated bug https://bugzilla.redhat.com/show_bug.cgi?id=1187526

Comment 3 Niels de Vos 2015-04-13 12:05:53 UTC
(In reply to Frank Lu from comment #2)
> duplicated bug https://bugzilla.redhat.com/show_bug.cgi?id=1187526

Thanks!

*** This bug has been marked as a duplicate of bug 1187526 ***