Bug 1561680

Summary:	[GSS] LVM archives on gluster pod fill up root directory.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Cal Calhoun <ccalhoun>
Component:	heketi	Assignee:	Niels de Vos <ndevos>
Status:	CLOSED ERRATA	QA Contact:	vinutha <vinug>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhgs-3.3	CC:	akhakhar, akrishna, annair, bkunal, dyocum, hchiramm, jarrpa, jmulligan, madam, ndevos, pprakash, rcyriac, rhs-bugs, rreddy, rtalur, sankarshan, storage-qa-internal
Target Milestone:	---
Target Release:	CNS 3.10
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	heketi-6.0.0-14.el7rhgs	Doc Type:	Bug Fix
Doc Text:	Previously, when PVCs were created/deleted in environments that are managed by Heketi, the LVM-metadata backups resulted in large storage consumption under /etc/lvm/archive which resulted in the filesystem running out of space. With this fix, Heketi no longer creates backups of LVM-metadata by default. This configuration can be changed by editing the `backup_lvm_metadata: true` variable in the heketi.json configuration file.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-12 09:22:12 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:
Bug Depends On:
Bug Blocks:	1568861, 1573420, 1638888, 1641915, 1642792

Comment 3 Niels de Vos 2018-05-17 16:49:42 UTC

There is very little use of the lvm archives for actions that heketi does. Users are not expected to need to restore a VG/LV, they would rather replace the brick and have Gluster repair/heal the data.

We can prevent creating the lvm archive by passing --autobackup=n to vgcreate/lvcreate.

Comment 13 Anjana KD 2018-08-30 13:52:22 UTC

Updated doc text in the Doc Text field. Please review for technical accuracy.

Comment 14 John Mulligan 2018-09-07 18:29:36 UTC

Doc Text looks OK

Comment 16 errata-xmlrpc 2018-09-12 09:22:12 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/RHEA-2018:2686

Comment 17 Raghavendra Talur 2019-11-08 19:32:11 UTC

*** Bug 1638888 has been marked as a duplicate of this bug. ***