Bug 1238171 – Not able to recover the corrupted file on Replica volume

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1238171 - Not able to recover the corrupted file on Replica volume

Summary:	Not able to recover the corrupted file on Replica volume

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Gluster Storage
Classification:	Red Hat
Component:	bitrot (Show other bugs)
Sub Component:
Version:	3.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity high
Target Milestone:	---
Target Release:	RHGS 3.1.1
Assigned To:	Raghavendra Bhat
QA Contact:	RajeshReddy
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Duplicates:	1266014 1266015 (view as bug list)
Depends On:
Blocks:	1216951 1238188 1251815 1255604 1255689 1266014 1266015
	Show dependency tree / graph

Reported:	2015-07-01 06:40 EDT by RajeshReddy
Modified:	2018-03-13 05:59 EDT (History)
CC List:	9 users (show)

See Also:
Fixed In Version:	glusterfs-3.7.1-13
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Clones:	1238188 1266014 1266015 (view as bug list)
Environment:
Last Closed:	2015-10-05 03:17:37 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2015:1845	normal	SHIPPED_LIVE	Moderate: Red Hat Gluster Storage 3.1 update	2015-10-05 07:06:22 EDT

Groups: None (edit)

Description RajeshReddy 2015-07-01 06:40:26 EDT

Description of problem:
=======================
Not able to recover the corrupted file on Replica volume 


Version-Release number of selected component (if applicable):
==========
glusterfs-api-3.7.1-6

How reproducible:


Steps to Reproduce:
==========================
1.Create 1X2 volume and enable bitrot, once the file is signed modify the file directly from the brick on any of the node
2.Once scrubber marks the file as bad , trying to recover the file by running following steps

3. Get the gfid of the corrupted file by running the getfattr -d -m . -e hex <filename>
4. Delete the corrupted file directly from the back-end
5. Go to the /brick/.glsuterfs and delete the gfid file
6. From the FUSE mount access the corrupted file 
7. Run gluster volume heal volname to get the deleted corrupted file

Actual results:
Self heal is failing 

Expected results:
User should be able to recover the bad file 

Setup details:
IP:10.70.36.26/29

Comment 2 monti lawrence 2015-07-22 15:37:58 EDT

Doc text is edited. Please sign off to be included in Known Issues.

Comment 3 Venky Shankar 2015-07-27 02:21:14 EDT

doc text looks good.

Comment 9 RajeshReddy 2015-08-31 05:25:21 EDT

Tested with "glusterfs-server-3.7.1-12", able to recover the bad file from the replica volume so marking this as verified

Comment 10 RajeshReddy 2015-09-09 08:50:02 EDT

Tested with 3.1.1 build and manually able to recover the bad file from replica volume

Comment 12 errata-xmlrpc 2015-10-05 03:17:37 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-1845.html

Comment 13 Nagaprasad Sathyanarayana 2016-01-16 22:39:50 EST

*** Bug 1266014 has been marked as a duplicate of this bug. ***

Comment 15 Amar Tumballi 2018-03-13 05:59:15 EDT

*** Bug 1266015 has been marked as a duplicate of this bug. ***

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