Bug 861367

Summary:	[FEAT REQ] Make fstab entry for brick lvms
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Anush Shetty <ashetty>
Component:	rhsc	Assignee:	Sahina Bose <sabose>
Status:	CLOSED DUPLICATE	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	medium	Docs Contact:
Priority:	low
Version:	2.0	CC:	dtsang, knarra, mmahoney, rhs-bugs, ssampat, vbellur
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-23 11:31:17 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 Anush Shetty 2012-09-28 11:20:39 UTC

Description of problem: Volume create should make a fstab entry for lvms used as bricks in gluster volumes.


Version-Release number of selected component (if applicable): RHS 2.0


How reproducible: N/A


Steps to Reproduce:
1.
2.
3.
  
Actual results:

Doesn't make an entry in /etc/fstab.


Expected results:

Should create an entry in /etc/fstab

Additional info:

Comment 2 Amar Tumballi 2012-10-22 02:42:37 UTC

can you be more elaborate on this? I personally think glusterfs should not deal with messing around with system files (like /etc/fstab).

Meantime, if its an issue for you in RHS, we can bring a commit hook for create volume to achieve this. Please provide more details.

Challenge is what if the same mount point is used as brick in multiple volume? etc.. etc...

Comment 3 Anush Shetty 2013-01-15 06:03:17 UTC

It is just an usability issue. You create a volume and mount the volume. But when a user forgets to make an fstab entry, if the machine reboots for some reason it ends up writing the data somewhere else.

Comment 5 Sahina Bose 2015-01-23 11:31:17 UTC


*** This bug has been marked as a duplicate of bug 850463 ***