Bug 1242442

Summary:	Restoring volume should change fstab entry
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Stanislav Graf <sgraf>
Component:	rhsc	Assignee:	Sahina Bose <sabose>
Status:	CLOSED CANTFIX	QA Contact:	RHS-C QE <rhsc-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	asriram, nlevinki, rhs-bugs, sabose, sankarshan
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	Restoring a volume to a snapshot changes the volume to use the snapshot bricks mounted at /var/run/gluster/snaps/. However, it does not remove the /etc/fstab entries for the original brick. This could cause a RHEL-7 system to fail to boot. Workaround: 1. Ensure that /etc/fstab entries are removed when the LVs are deleted from system. 2. If the system fails to boot, then start the system in emergency mode, use the root password, remount '/' in rw, edit fstab, save it, and then reboot.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-01-30 11:40:01 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:	1216951

Description Stanislav Graf 2015-07-13 10:59:34 UTC

Description of problem:
=======================

When we restore a volume to the previously created snapshot, we create a 'regular volume' from the above 'snap' volume, which has the same name and 
volume-id as the original volume. Hence after restore you see the volume 
has bricks like /var/run/gluster/snaps/<snap-id>.

--> this should be reflected also in /etc/fstab

Comment 3 monti lawrence 2015-07-23 16:00:51 UTC

Doc text is edited. Please sign off to be included in Known Issues.

Comment 4 Ramesh N 2015-07-24 11:07:18 UTC

doc text looks good. Approved.

Comment 7 Sahina Bose 2018-01-30 11:40:01 UTC

Thank you for your bug report. However, this bug is being closed as it's on a component where no further new development is being undertaken.