| Summary: | stat of a deleted file throwing Input/output error | ||
|---|---|---|---|
| Product: | Red Hat Gluster Storage | Reporter: | Nag Pavan Chilakam <nchilaka> |
| Component: | gluster-nfs | Assignee: | Jiffin <jthottan> |
| Status: | CLOSED WONTFIX | QA Contact: | Manisha Saini <msaini> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.2 | CC: | rhs-bugs, skoduri, storage-qa-internal |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-19 04:11:54 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: | |
[root@dhcp35-37 ~]# rpm -qa|grep gluster gluster-nagios-common-0.2.4-1.el7rhgs.noarch glusterfs-server-3.8.4-3.el7rhgs.x86_64 glusterfs-ganesha-3.8.4-3.el7rhgs.x86_64 glusterfs-api-3.8.4-3.el7rhgs.x86_64 glusterfs-libs-3.8.4-3.el7rhgs.x86_64 glusterfs-client-xlators-3.8.4-3.el7rhgs.x86_64 nfs-ganesha-gluster-2.3.1-8.el7rhgs.x86_64 glusterfs-cli-3.8.4-3.el7rhgs.x86_64 python-gluster-3.8.4-3.el7rhgs.noarch glusterfs-devel-3.8.4-3.el7rhgs.x86_64 glusterfs-events-3.8.4-3.el7rhgs.x86_64 glusterfs-geo-replication-3.8.4-3.el7rhgs.x86_64 glusterfs-fuse-3.8.4-3.el7rhgs.x86_64 glusterfs-api-devel-3.8.4-3.el7rhgs.x86_64 glusterfs-rdma-3.8.4-3.el7rhgs.x86_64 gluster-nagios-addons-0.2.7-1.el7rhgs.x86_64 glusterfs-3.8.4-3.el7rhgs.x86_64 hit this bug as part of validation of 1328451 - observing " Too many levels of symbolic links" after adding bricks and then issuing a replace brick |
1)create a distributed volume with 2 bricks and mount volume on two gnfs clients say c1 and c2 2)created a dir say dir1 3)now create files f{1..10}, and in backend check which file hashes to which brick 4)delete all files 5)now from backend create a file f1 on the brick which it DOESNT hash to 6) now from client c1 and c2 do "ls f1" expected: lookup must pass backend brick which the file was supposed to be hashed to must have a link to file created 7)now delete f1 from client 8)then do a ls f1 ls list the file now delete f1 from c1 and do stat f1 from c2 c2 throws stat: cannot stat ‘f1’: Input/output error it must instead throw no such file or dir