| Summary: | Look up should trigger Data Self heal of missing files (with GFID's) on the bricks | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Shwetha Panduranga <shwetha.h.panduranga> | ||||||
| Component: | replicate | Assignee: | Pranith Kumar K <pkarampu> | ||||||
| Status: | CLOSED WORKSFORME | QA Contact: | |||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | mainline | CC: | gluster-bugs, vbellur | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-03-01 12:22:25 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
With master head 6e9a8f61b7d7371fa749c168162c716c2b0be70b It worked fine for me. ls -l [root@pranithk-laptop ~]# ls -l /mnt/repl2 total 8 -rw-r--r--. 1 root root 0 Mar 1 17:49 a -rw-r--r--. 1 root root 0 Mar 1 17:49 b pranithk @ ~ 17:50:52 :) $ ls -l /gfs/repl2_?/ /gfs/repl2_0/: total 8 -rw-r--r--. 2 root root 0 Mar 1 17:49 a -rw-r--r--. 2 root root 0 Mar 1 17:50 b /gfs/repl2_1/: total 8 -rw-r--r--. 2 root root 0 Mar 1 17:49 a -rw-r--r--. 2 root root 0 Mar 1 17:50 b Created attachment 566837 [details]
testcase execution log
Test Case is now passing in the automation run too. |
Created attachment 560163 [details] test case execution log Description: missing files with GFID's on bricks (files present on brick1 not present on brick2 and vice verse) has to be forced merged Version-Release number of selected component (if applicable): 3.3.0qa21 How reproducible: Frequently Steps to Reproduce: From Backend: ------------ 1.Create a file1 on brick1 2.Assign GFID to file1 3.Create a file2 on brick2 4.Assign GFID to file2 5.Create a replicate volume with brick1, brick2 6.Start the volume From MountPoint. --------------- 1. ls -l Actual results: 1. Triggers only entry self-heal. The file entries are selfhealed even though the xattrs are set for data self-heal of the files on both the bricks Expected results: 1. Should Trigger and complete entry and data self-heal. Force merging of files. Additional info: ls -l from mount point for first time triggers entry-self only.if ls -l is executed from mount point again, the data self-heal is triggered.