[Gluster-devel] BitRot: detection of files changes

Попов О.В. o.popov at livelace.ru
Sun Oct 4 16:25:52 UTC 2015


Hello.

Version:

[root at glusterfs1 ~]# rpm -qa | grep gluster
glusterfs-client-xlators-3.7.4-2.el7.x86_64
glusterfs-cli-3.7.4-2.el7.x86_64
glusterfs-3.7.4-2.el7.x86_64
glusterfs-geo-replication-3.7.4-2.el7.x86_64
glusterfs-fuse-3.7.4-2.el7.x86_64
glusterfs-server-3.7.4-2.el7.x86_64
glusterfs-libs-3.7.4-2.el7.x86_64
glusterfs-api-3.7.4-2.el7.x86_64

Configuration of volume:

[root at glusterfs2 ~]# gluster volume info ovirt-data

Volume Name: ovirt-data
Type: Replicate
Volume ID: a1faaa53-c53e-4696-a078-0e1f4e2444a2
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: 10.0.102.6:/export/vdb1/ovirt-data
Brick2: 10.0.102.7:/export/vdb1/ovirt-data
Brick3: 10.0.102.8:/export/vdb1/ovirt-data
Options Reconfigured:
server.allow-insecure: on
storage.owner-gid: 36
storage.owner-uid: 36
performance.readdir-ahead: on
geo-replication.indexing: on
geo-replication.ignore-pid-check: on
changelog.changelog: on
cluster.quorum-count: 1
cluster.quorum-type: fixed
network.ping-timeout: 1
features.bitrot: on
features.scrub: Active
features.scrub-freq: hourly
features.scrub-throttle: aggressive

On glusterfs1:

mount -t glusterfs 10.0.102.6:/ovirt-data /mnt
dd if=/dev/urandom of=/mnt/file bs=1M count=100
md5sum /export/vdb1/ovirt-data/file
0b093e9f1524cde2d64ce0a105237190  /export/vdb1/ovirt-data/file

On glusterfs3:

dd if=/dev/urandom of=/export/vdb1/ovirt-data/file bs=1M count=100
md5sum /export/vdb1/ovirt-data/file
af0fee68511176b7fcac6cbbd3137431  /export/vdb1/ovirt-data/file

Logs of scrub and bitd attached.

Question: why changes was not detected and how should be process of 
detection of broken files (denied access/read-only mode etc) ?

-- 
С уважением, Попов О.В. / Best regards, Popov V Oleg

tel: +7 981 783-90-13
skype: livelace

-------------- next part --------------
A non-text attachment was scrubbed...
Name: glusterfs1-bitd.log
Type: text/x-log
Size: 31070 bytes
Desc: not available
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20151004/39992a46/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: glusterfs1-scrub.log
Type: text/x-log
Size: 29854 bytes
Desc: not available
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20151004/39992a46/attachment-0005.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: glusterfs3-bitd.log
Type: text/x-log
Size: 31070 bytes
Desc: not available
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20151004/39992a46/attachment-0006.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: glusterfs3-scrub.log
Type: text/x-log
Size: 29854 bytes
Desc: not available
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20151004/39992a46/attachment-0007.bin>


More information about the Gluster-devel mailing list