Bug 1757801

Summary: [GSS] errors reading a chunk in gluster volume ErrNo.2.(No such file or directory)-Open failed
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: amansan <amanzane>
Component: distributeAssignee: Csaba Henk <csaba>
Status: CLOSED ERRATA QA Contact: Pranav Prakash <prprakas>
Severity: urgent Docs Contact:
Priority: urgent    
Version: rhgs-3.4CC: aloganat, csaba, olim, pprakash, prprakas, puebele, ravishankar, rhs-bugs, sabose, saraut, sheggodu, skandark, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.5.z Batch Update 4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-6.0-50 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-29 07:20:36 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 amansan 2019-10-02 13:24:09 UTC
Description of problem:

When the customer were attempting to restore critical data they experienced errors reading a chunk on Gluster Storage

Comment 7 amansan 2019-10-03 10:42:12 UTC
Good morning

The option is set to on as expected, the customer agrees to turn it off but as they are still restoring information they are worried about the impact this change can done.

They are seeing poor performance on the reads so they are concerned about how this option could impact.

Is it safe to execute it now? or should we wait till the restore finish ?

Thanks

Alicia

Comment 8 Raghavendra G 2019-10-03 12:04:16 UTC
(In reply to amansan from comment #7)
> Good morning
> 
> The option is set to on as expected, the customer agrees to turn it off but
> as they are still restoring information they are worried about the impact
> this change can done.
> 
> They are seeing poor performance on the reads so they are concerned about
> how this option could impact.

Turning off this option would result in slowdown of lookups. If there are lots of small files, then reading them would also become slow as opening an fd to read the file would involve lookup. However, if the number of files is less (like small number of large files), performance impact on reading files would be less.

> 
> Is it safe to execute it now? or should we wait till the restore finish ?

If cu is ok to live with this problem till restore is done, we can turn off the option post restore. However, if the problem is severely affecting them, they can turn off the option and see whether they can live with the resultant performance.

> 
> Thanks
> 
> Alicia

Comment 29 errata-xmlrpc 2021-04-29 07:20:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (glusterfs bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1462