[Bugs] [Bug 1152957] arequal-checksum mismatch between before and after successful heal on a replaced disk

bugzilla at redhat.com bugzilla at redhat.com
Mon Nov 3 05:32:53 UTC 2014


https://bugzilla.redhat.com/show_bug.cgi?id=1152957

Krutika Dhananjay <kdhananj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kdhananj at redhat.com
              Flags|                            |needinfo?(spandura at redhat.c
                   |                            |om)



--- Comment #2 from Krutika Dhananjay <kdhananj at redhat.com> ---
Tried reproducing this bug several times but to no avail with release-3.6
branch with the head being at commit 3867bdb496b9a34ab3db06c151e822aa9379b3e9.

Here's what I did:

1. Created a 2x2 dis-rep volume on a 4-node cluster with one brick on each
node, started and mounted on a different node.

2) Ran the scripts to create symlinks and hardlinks attached with BZ 1117167:

[root at nestor mnt]#~/hard_link_self_heal.sh /mnt create_files_and_dirs blah_1
[root at nestor mnt]~/hard_link_self_heal.sh /mnt create_hard_links blah_1

[root at nestor mnt]#~/sym_link_self_heal.sh /mnt create_files_and_dirs blah_2
[root at nestor mnt]#~/sym_link_self_heal.sh /mnt create_sym_links blah_2
[root at nestor mnt]#~/sym_link_self_heal.sh /mnt add_files_from_sym_links blah_2

3) Computed arequal-checksum at this point on the mountpoint.

3) Executed `pkill gluster` on the node containing the third brick. Removed the
brick directory, recreated it and set the volume-id xattr on it.

4) Started glusterd service on node 3.

5) Executed `heal full` from one of the nodes.

6) After some time, computed arequal checksum on brick-3 and brick-4, and
compared the output.

Result: Both checksums matched. Even the arequal-checksum on the mount is same
after heal.

Shwetha,

Could you let me know if the steps look OK or whether there is something I need
to do differently here?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=s8SPFOkFmC&a=cc_unsubscribe


More information about the Bugs mailing list