Bug 1396328
Summary: | after write some files into the gluster DFS volume successful, when we read one of these files will warn cannot get the file stat,but other file can read | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | q449278118 <1352411423> |
Component: | distribute | Assignee: | Nithya Balachandran <nbalacha> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.6.3 | CC: | 1352411423, bugs |
Target Milestone: | --- | Keywords: | Triaged |
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: | 2016-12-02 06:41:03 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
q449278118
2016-11-18 02:54:46 UTC
int the brick of bad file, we use ls -l,we can see the bad files link counts is 1,and the other good files is 2,and we can read the bad files; but,in the gluster mount point, use ls -l,we can see the bad files counts is 0,and the other good files is 1,and the bad file cannot read. (In reply to q449278118 from comment #1) > int the brick of bad file, we use ls -l,we can see the bad files link > counts is 1,and the other good files is 2,and we can read the bad files; > but,in the gluster mount point, use ls -l,we can see the bad files > counts is 0,and the other good files is 1,and the bad file cannot read. Can you provide the following: 1. gluster volume info for the volume 2. How many clients you are using. Are you using the same client to write and read from the file 3. ls output 4. OS and filesystem you are using for both server and clients This bug is getting closed because the 3.6 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. (In reply to Nithya Balachandran from comment #2) > (In reply to q449278118 from comment #1) > > int the brick of bad file, we use ls -l,we can see the bad files link > > counts is 1,and the other good files is 2,and we can read the bad files; > > but,in the gluster mount point, use ls -l,we can see the bad files > > counts is 0,and the other good files is 1,and the bad file cannot read. > > Can you provide the following: > > 1. gluster volume info for the volume > 2. How many clients you are using. Are you using the same client to write > and read from the file > 3. ls output > 4. OS and filesystem you are using for both server and clients 1 three bricks with distribute volume without replicate 2 only one client, read and write 3 output as I expressed topic, 1 brick a file hard link 0, but others 1 4 redhat7.0 as the server and client,client mapped volume with NFS and USERS use NFS client to access the volume; 5 when we remove the brick (which has some files hard link 0),the bad error disappeard |