Bug 1461131 - [RFE] gid is not found for volumes created using heketi < v5
[RFE] gid is not found for volumes created using heketi < v5
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: heketi (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Raghavendra Talur
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2017-06-13 10:54 EDT by Raghavendra Talur
Modified: 2018-03-11 13:23 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
Volumes that were created using CNS 3.5 or previous don't have the GID stored in heketi database. Hence, when a volume expansion is performed, new bricks don't get the group id set on them which might lead to I/O errors. To fix this please refer to the knowledge base article at:...
Story Points: ---
Clone Of:
Last Closed: 2018-01-18 06:38:12 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Raghavendra Talur 2017-06-13 10:54:21 EDT
Description of problem:
If a volume was created using heketi 3.* version and then a volume expansion is performed then the new bricks won't acquire the gid of the volume.
Comment 2 Humble Chirammal 2017-06-15 01:34:14 EDT
Ragavendra, Do you plan to land the patch for gid collection in heketi via this bugzilla ? if yes, are we targetting it for CNS 3.6 ?
Comment 3 Humble Chirammal 2017-08-02 10:13:10 EDT
This is an RFE, so I am moving out of this release.
Comment 4 Prasanth 2017-10-04 13:06:44 EDT
Bhavana, this BZ should be documented as a known issue for CNS 3.6 release and so please do the needful.
Comment 5 Humble Chirammal 2018-01-18 06:38:12 EST
I am closing this bug as this feature is available in current release and also in previous releases since heketi v4 . We dont have any plan to backport this to very old releases of heketi.

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