Bug 1638623 - Revert XFS related changes from gdeploy
Summary: Revert XFS related changes from gdeploy
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gdeploy
Version: rhgs-3.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHGS 3.4.z Batch Update 1
Assignee: Sachidananda Urs
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1638622
TreeView+ depends on / blocked
 
Reported: 2018-10-12 06:05 UTC by SATHEESARAN
Modified: 2018-10-31 08:42 UTC (History)
6 users (show)

Fixed In Version: gdeploy-2.0.2-30.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1638622
Environment:
Last Closed: 2018-10-31 08:42:22 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1578354 0 high CLOSED [RFE] Change xfs settings when vdo volume is used 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2018:3430 0 None None None 2018-10-31 08:42:38 UTC

Internal Links: 1578354

Description SATHEESARAN 2018-10-12 06:05:51 UTC 
Description of problem:
-----------------------
Bug 1523562 was fixed to include XFS max_retries for the case of XFS on VDO volumes. With the information from Bryan Gurney on the bug 1578353, this change is no longer required.

This bug is filed to have that earlier XFS max_retries change to be removed

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
gdeploy-2.0.2-29

How reproducible:
-----------------
Always

Expected results:
------------------
Remove the change that came in with effect of BZ 1523562
Comment 1 Sachidananda Urs 2018-10-15 09:58:24 UTC 
PR: https://github.com/gluster/gdeploy/pull/518 fixes the issue
Comment 3 SATHEESARAN 2018-10-17 10:17:24 UTC 
Tested with glustter-ansible-roles-1.0.3 

XFS  max_retries  changes are not changed to post deployment.

# cat /sys/fs/xfs/dm-16/error/metadata/ENOSPC/max_retries
-1
Comment 5 errata-xmlrpc 2018-10-31 08:42:22 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, 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-2018:3430
Note You need to log in before you can comment on or make changes to this bug.