Bug 1444108

Summary: ls: cannot access 'file': No data available. In log Error --> buf->ia_gfid is null for
Product: [Community] GlusterFS Reporter: Radhakrishnan <rradhakrishnan95>
Component: unclassifiedAssignee: bugs <bugs>
Status: CLOSED EOL QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.8CC: bugs, rkavunga, rradhakrishnan95
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-07 10:39:47 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:
Attachments:
Description Flags
Word file none

Description Radhakrishnan 2017-04-20 15:09:42 UTC
Created attachment 1273003 [details]
Word file

Description of problem:
Using Glusterfs 3.7.6,I mounted the volume and that files are replicated to the nodes. But i'm facing Data Not Found Error.


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


How reproducible:
Tried once.

Steps to Reproduce:
1.umount the volume.
2.checked the file permissions.
3.

Actual results:
 No data available,Can't access it


Expected results:


Additional info:
E [MSGID: 113002] [posix.c:206:posix_lookup] 0-datapoint-posix: buf->ia_gfid is null for /var/rad/l [No data available]
[2017-04-20 12:30:52.687659] E [MSGID: 115050] [server-rpc-fops.c:178:server_lookup_cbk] 0-datapoint-server: 2150: LOOKUP /l (00000000-0000-0000-0000-000000000001/l) ==> (No data available) [No data available]

Comment 1 Mohammed Rafi KC 2017-05-02 12:27:15 UTC
Can you provide us some steps to reproduce ?

Comment 2 Niels de Vos 2017-05-02 12:29:58 UTC
You will need to provide more details on what you are doing. The message in the log indicates that a file called "l" on the root of the volume was tried to be accessed, and that file did not exist.

Note that GlusterFS 3.7 is End-Of-Life and will not receive any updates anymore. Please verify if you have the same problem (which is not described clearly) on version 3.8, 3.10 or newer.

Comment 3 Niels de Vos 2017-11-07 10:39:47 UTC
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.

Comment 4 Red Hat Bugzilla 2023-09-14 03:56:41 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days