Re: bitrot error correction in gluster 3.8 distributed dispersed setup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Hi,

"gluster v heal" command does not heal corrupt files detected by bitrot feature.
You have modified a file from back end and corrupted it.

I think to correct your corrupted files (in fact the part of file in case of disperse volume) you have to delete that part and run gluster v heal <volname> full
to correct the file.

Keeping Kotresh in cc for better input of bitrot.

Ashish



From: "itlinux_team" <itlinux@xxxxxxxxx>
To: gluster-users@xxxxxxxxxxx
Sent: Wednesday, July 20, 2016 7:43:56 PM
Subject: [Gluster-users] bitrot error correction in gluster 3.8 distributed        dispersed setup

Hi all,

I'm testing the bitrot feature on a distributed dispersed setup:  3 x (8
+ 4).
I simulated a bit-flip on the part of a couple of files in a brick,
having bitrot feature enabled before. The output from ''gluster volume
bitrot vol_1 scrub status'' shows that two files are corrupted as shown
below:


---
Volume name : vol_1

State of scrub: Active

Scrub impact: normal

Scrub frequency: daily

Bitrot error log location: /var/log/glusterfs/bitd.log

Scrubber error log location: /var/log/glusterfs/scrub.log


=========================================================

Node: localhost

Number of Scrubbed files: 564

Number of Skipped files: 0

Last completed scrub time: 2016-07-20 13:37:16

Duration of last scrub (D:M:H:M:S): 0:0:0:50

Error count: 0


=========================================================

Node: glusterserver1

Number of Scrubbed files: 562

Number of Skipped files: 0

Last completed scrub time: 2016-07-20 13:37:16

Duration of last scrub (D:M:H:M:S): 0:0:0:51

Error count: 2

Corrupted object's [GFID]:

e3cbffbe-12bd-4e1c-8dcf-2ef87ac99990

2550475e-cf9e-4781-9a05-9e11c1dd6b7a


=========================================================

Node: glusterserver3

Number of Scrubbed files: 564

Number of Skipped files: 0

Last completed scrub time: 2016-07-20 13:37:16

Duration of last scrub (D:M:H:M:S): 0:0:0:50
---


I have executed ''gluster volume heal vol_1 full'' but it does not seem
to fix the files, however the file that the client reads is the correct
one.

How should I handle this kind of corruption within gluster?

Thanks!
Iñaki.

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux