Bug 1665332 - Wrong offset is used in offset for zerofill fop
Summary: Wrong offset is used in offset for zerofill fop
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-11 01:48 UTC by Pranith Kumar K
Modified: 2019-03-25 16:33 UTC (History)
1 user (show)

Fixed In Version: glusterfs-6.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-25 16:33:00 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 21991 0 None Merged cluster/afr: fix zerofill transaction.start 2019-01-14 03:20:49 UTC

Description Pranith Kumar K 2019-01-11 01:48:17 UTC
Description of problem:

in afr_zerofill()
{
local->transaction.start = local->cont.discard.offset; //--> s/discard/zerofill/
}

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2019-01-11 01:50:19 UTC
REVIEW: https://review.gluster.org/21991 (cluster/afr: fix zerofill transaction.start) posted (#3) for review on master by Pranith Kumar Karampuri

Comment 2 Worker Ant 2019-01-14 03:20:49 UTC
REVIEW: https://review.gluster.org/21991 (cluster/afr: fix zerofill transaction.start) posted (#5) for review on master by Pranith Kumar Karampuri

Comment 3 Shyamsundar 2019-03-25 16:33:00 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report.

glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/


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