Bug 1736564 - GlusterFS files missing randomly.
Summary: GlusterFS files missing randomly.
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: 6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-01 18:56 UTC by yexue2015
Modified: 2020-03-12 12:13 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-12 12:13:29 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description yexue2015 2019-08-01 18:56:05 UTC
Description of problem:
Some files were suddenly missing. Then after a couple of days, the missing files appeared again (not been damaged).

Under one of my folders, there were two sub-folders and four files. At a point, two files were missing and more files under those two sub-folders were missing randomly. There should be 210 files under each of the sub-folders, but after the missing occurs, there were 125 and 138 files left. I can no longer read the files that are missing. However, after a few days. I found the missing files were back.

Version-Release number of selected component (if applicable):
rpm -qa | grep glusterfs
glusterfs-6.1-1.el7.x86_64
glusterfs-client-xlators-6.1-1.el7.x86_64
glusterfs-libs-6.1-1.el7.x86_64
glusterfs-fuse-6.1-1.el7.x86_64

How reproducible:
The problem occurs quite randomly. It is not clear what triggers the missing and how to reproduce the problem.

Steps to Reproduce:
1. NA

Actual results:
NA

Expected results:
NA

Additional info:

Comment 1 Amar Tumballi 2019-08-05 05:29:39 UTC
Can you try below command see if that helps?

'gluster volume set <VOLNAME> parallel-readdir disable'

Comment 2 Worker Ant 2020-03-12 12:13:29 UTC
This bug is moved to https://github.com/gluster/glusterfs/issues/843, and will be tracked there from now on. Visit GitHub issues URL for further details


Note You need to log in before you can comment on or make changes to this bug.