Bug 1289437
Summary: | [Tier]: rm -rf * from client during demotion causes a stale link file to remain in system with attributes as ????? | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Rahul Hinduja <rhinduja> |
Component: | tier | Assignee: | Mohammed Rafi KC <rkavunga> |
Status: | CLOSED ERRATA | QA Contact: | Rahul Hinduja <rhinduja> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.1 | CC: | nchilaka, rhs-bugs, rkavunga, sankarshan, storage-qa-internal |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | RHGS 3.1.2 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.7.5-12 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-01 06:02:11 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1276227 | ||
Bug Blocks: | 1260783 |
Description
Rahul Hinduja
2015-12-08 06:27:26 UTC
upstream patch : http://review.gluster.org/#/c/12829/ Verified with build: glusterfs-3.7.5-12 While promotion and demotiones were inprogress, performed rm -rf * from client having 6k files at 5 level deep directory. All files got removed from client and backend without any stale file being present in the system. Moving this bug to verified state. From Client: ============ [root@dj fuse]# ls t1 test thread0 thread1 thread2 thread3 thread4 [root@dj fuse]# [root@dj fuse]# [root@dj fuse]# rm -rf * [root@dj fuse]# [root@dj fuse]# ls -lRt .: total 0 [root@dj fuse]# From Backend: ============= Cold Tier bricks: ================= [root@dhcp37-165 tiervolume_ct-disp1]# ls -lRt .: total 0 [root@dhcp37-165 tiervolume_ct-disp1]# [root@dhcp37-133 tiervolume_ct-disp1]# ls -lRt .: total 0 [root@dhcp37-133 tiervolume_ct-disp1]# [root@dhcp37-160 tiervolume_ct-disp1]# ls -lRt .: total 0 [root@dhcp37-160 tiervolume_ct-disp1]# [root@dhcp37-158 tiervolume_ct-disp1]# ls -lRt .: total 0 [root@dhcp37-158 tiervolume_ct-disp1]# [root@dhcp37-110 tiervolume_ct-disp1]# ls -lRt .: total 0 [root@dhcp37-110 tiervolume_ct-disp1]# [root@dhcp37-155 tiervolume_ct-disp1]# ls -lRt .: total 0 [root@dhcp37-155 tiervolume_ct-disp1]# Hot Tier Bricks: ================ [root@dhcp37-99 tiervolume_hot]# ls -lRt .: total 0 [root@dhcp37-99 tiervolume_hot]# [root@dhcp37-88 tiervolume_hot]# ls -lRt .: total 0 [root@dhcp37-88 tiervolume_hot]# [root@dhcp37-112 tiervolume_hot]# ls -lRt .: total 0 [root@dhcp37-112 tiervolume_hot]# [root@dhcp37-199 tiervolume_hot]# ls -lRt .: total 0 [root@dhcp37-199 tiervolume_hot]# [root@dhcp37-162 tiervolume_hot]# ls -lRt .: total 0 [root@dhcp37-162 tiervolume_hot]# [root@dhcp37-87 tiervolume_hot]# ls -lRt .: total 0 [root@dhcp37-87 tiervolume_hot]# 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/RHBA-2016-0193.html |