Bug 1730019 - Don't allow volume expansion or resize on volume with snapshots
Summary: Don't allow volume expansion or resize on volume with snapshots
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: snapshot
Version: ocs-3.11
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Srijan Sivakumar
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-15 15:22 UTC by ktenzer
Modified: 2021-07-29 11:31 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-29 11:31:45 UTC
Embargoed:


Attachments (Terms of Use)

Description ktenzer 2019-07-15 15:22:46 UTC
Description of problem:
Create a snapshot of a volume and then grow the volume. It works. Yet this can cause instability and it is documented should never be done.


Version-Release number of selected component (if applicable):
OCS 3.11 but all versions of gluster I suppose


How reproducible:
100%

Steps to Reproduce:
1. create snapshot on volume
2. grow volume

Actual results:
It works


Expected results:
It should fail because we dont want a volume which has snapshots to be expanded or grown.


Additional info:

Comment 2 Patric Uebele 2019-07-19 09:42:04 UTC
As this is in the context of OCS, would heketi perhaps be the better component to address this?

Comment 3 Atin Mukherjee 2019-07-22 04:13:08 UTC
(In reply to Patric Uebele from comment #2)
> As this is in the context of OCS, would heketi perhaps be the better
> component to address this?

Even though this request has originated from OCS, but this is applicable for standalone RHGS too IMO and hence such extra validations should get added in core Gluster is what I believe.

Comment 5 ktenzer 2020-03-03 08:45:04 UTC
A warning message is better than nothing for sure.

Comment 6 Mohammed Rafi KC 2020-03-11 20:03:16 UTC
upsteam patch: https://review.gluster.org/#/c/glusterfs/+/24213/


Note You need to log in before you can comment on or make changes to this bug.