Bug 1779616
| Summary: | Glusterfs mount-dir is getting read-only system after 1 day | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | sharmaakshay890 |
| Component: | posix | Assignee: | Mohammed Rafi KC <rkavunga> |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5 | CC: | bugs, pasik, rkavunga, sabose |
| 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: | 2020-03-12 12:29: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: | |
| Embargoed: | |||
|
Description
sharmaakshay890
2019-12-04 11:34:10 UTC
Rafi, can you take a look? It looks like the backend brick mount is corrupted. The system logs suggest an i/o error, and mostly due to a hardware failure or will be related to the storage device. The errors from gluster brick logs are also from the POSIX layer, the layer where gluster talks to the backend device. So it is highly likely to have some problems with the backend mount. Thanks Rafi, 1). Can i know what could be reason of this i/o error failure??. We are facing this issues in some of the machines , due to which we are unable to do anything until and unless we reboots that machine. After that everything come backs to normal. we are unable to find the root cause. 2). I have shared some steps in bug's Additional Info. can you please let us know, that mentioned steps are correct ? (for creation and cleaning up of Glusterfs). 3) Recommended Backend storage for glusterfs ?? we are using Sata disk with ext4 type. (In reply to sharmaakshay890 from comment #3) > Thanks Rafi, > > 1). Can i know what could be reason of this i/o error failure??. > > We are facing this issues in some of the machines , due to which we are > unable to do anything until and unless we reboots that machine. > After that everything come backs to normal. > > we are unable to find the root cause. I have to admit it I'm not an expert in disk failure cases. You can may start with the disk health check and then see if the file system is corrupted or not. > > 2). I have shared some steps in bug's Additional Info. > > can you please let us know, that mentioned steps are correct ? (for creation > and cleaning up of Glusterfs). Please refer to https://docs.gluster.org/en/latest/Administrator%20Guide/setting-up-storage/ > > 3) Recommended Backend storage for glusterfs ?? > > we are using Sata disk with ext4 type. ext4 is perfectly fine though gluster recommends XFS. This bug is moved to https://github.com/gluster/glusterfs/issues/896, and will be tracked there from now on. Visit GitHub issues URL for further details |