Back to bug 1311839

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-02-25 07:29:37 UTC Keywords ZStream
Sahina Bose 2016-02-25 07:30:40 UTC Blocks 1299184, 1258386
Pranith Kumar K 2016-03-01 11:27:41 UTC Status NEW ASSIGNED
Rahul Hinduja 2016-03-07 10:26:54 UTC CC rhinduja
Rejy M Cyriac 2016-03-08 07:50:53 UTC CC rcyriac
Red Hat Bugzilla Rules Engine 2016-03-08 08:16:44 UTC Target Release --- RHGS 3.1.3
Nag Pavan Chilakam 2016-03-15 11:34:02 UTC CC nchilaka
Rahul Hinduja 2016-03-27 15:00:27 UTC QA Contact storage-qa-internal nchilaka
Pranith Kumar K 2016-04-05 10:17:17 UTC Status ASSIGNED POST
Sahina Bose 2016-04-21 10:06:30 UTC Priority unspecified high
Pranith Kumar K 2016-04-21 11:33:58 UTC Status POST MODIFIED
Pranith Kumar K 2016-04-21 11:37:15 UTC Comment 5 is private 1 0
errata-xmlrpc 2016-05-02 06:02:28 UTC Status MODIFIED ON_QA
Satish Mohan 2016-05-02 06:06:42 UTC Fixed In Version glusterfs-3.7.9-3
Pranith Kumar K 2016-05-04 07:10:55 UTC Doc Text gluster volume heal <volname> info sometimes shows files that don't need heal as well in the output. This issue couldn't be fixed in a backward compatible manner. So for the fix to take effct, "gluster volume set <volname> locking-scheme granular" needs to be set on the volume.
Nag Pavan Chilakam 2016-05-26 12:20:39 UTC Status ON_QA VERIFIED
Laura Bailey 2016-06-06 07:24:39 UTC CC pkarampu
Doc Text gluster volume heal <volname> info sometimes shows files that don't need heal as well in the output. This issue couldn't be fixed in a backward compatible manner. So for the fix to take effct, "gluster volume set <volname> locking-scheme granular" needs to be set on the volume. When files, such as virtual machine metadata files, were updated very frequently, the 'gluster volume heal info' command sometimes listed files that did not require healing in its output. This could not be corrected in a backward-compatible way, so a new option has been added to implement the fix behavior. To ensure that false positives are not listed in the heal info output for a volume, use the following command to set a granular locking scheme for that volume:
# gluster volume set <volname> locking-scheme granular
Flags needinfo?(pkarampu)
Pranith Kumar K 2016-06-06 16:46:15 UTC Flags needinfo?(pkarampu)
Laura Bailey 2016-06-07 00:34:45 UTC Doc Text When files, such as virtual machine metadata files, were updated very frequently, the 'gluster volume heal info' command sometimes listed files that did not require healing in its output. This could not be corrected in a backward-compatible way, so a new option has been added to implement the fix behavior. To ensure that false positives are not listed in the heal info output for a volume, use the following command to set a granular locking scheme for that volume:
# gluster volume set <volname> locking-scheme granular
When files were being checked by the self heal daemon and the 'gluster volume heal info' command was run simultaneously, the command's output listed files that were being checked but not healed as possibly being healed. This could not be corrected in a backward-compatible way, so a new option has been added to implement the fix behavior. To ensure that false positives are not listed in the heal info output for a volume, use the following command to set a granular locking scheme for that volume:
# gluster volume set <volname> locking-scheme granular
errata-xmlrpc 2016-06-23 00:48:50 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-06-23 05:09:28 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-06-23 01:09:28 UTC
Rejy M Cyriac 2016-09-17 12:10:22 UTC CC rhs-bugs, storage-qa-internal
Component gluster-afr replicate

Back to bug 1311839