Bug 1335470 - Files not deleted from the arbiter brick after deletion from the mount point.
Summary: Files not deleted from the arbiter brick after deletion from the mount point.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: arbiter
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Ravishankar N
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1387494
TreeView+ depends on / blocked
 
Reported: 2016-05-12 09:37 UTC by Karan Sandha
Modified: 2018-11-19 07:45 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
: 1387494 (view as bug list)
Environment:
Last Closed: 2018-11-19 07:45:41 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
Mount point client (33.93 KB, image/png)
2016-05-12 09:37 UTC, Karan Sandha
no flags Details

Description Karan Sandha 2016-05-12 09:37:19 UTC
Created attachment 1156596 [details]
Mount point client

Description of problem:
The files from arbiter, brick1 got deleted after removing the files from the mount point. but the third brick the files were still remaining.


Version-Release number of selected component (if applicable):
Logs placed qe@@rhsqe-repo.lab.eng.blr.redhat.com:/var/www/html/sosreports

How reproducible: 1


Steps to Reproduce:
1. Mounted the volume on client  using fuse mount on server3(43.192)
2. created files using for ((i=1; i<=100; i++))
do
mkdir -pv directory$i
cd directory$i
dd if=/dev/urandom of=file$i bs=1M count=500 status=progress
cd ..
cd directory$i
echo "File Renamed"
mv file$i renamed$i

done

3. after the disk is full. delete the two files from directory1 and directory2.
4. shutdown the server2 (43.157) for 1 min.
5. Switch on the server and check for the files in all the bricks


Actual results:
files got deleted from arbiter43. and server2(43.157) but files remained undeleted from server3 (43.192)

files Undeleted:- 

[root@dhcp43-192 directory1]# ls
directory2  directory82  file82
[root@dhcp43-192 directory1]# cd directory2/
[root@dhcp43-192 directory2]# ls
directory3  directory81  file81
[root@dhcp43-192 directory2]# ls -ll
total 0
drwxr-xr-x. 4 root root 54 May 12 19:49 directory3
drwxr-xr-x. 2 root root  6 May 12 19:16 directory81
-rw-r--r--. 2 root root  0 May 12 19:16 file81

Expected results:
all files should be deleted from the servers  

Additional info:
Found this error while deleting the files from mount point.

root@dhcp42-93 fuse]# rm -rf directory1/
rm: cannot remove ‘directory1/directory2/directory3/directory4/directory5/directory6/directory7/directory8/directory9/directory10/directory11/directory12/directory13/directory14/directory15/directory16/directory17/directory18/directory19/directory20/directory21/directory22/directory23/directory24/directory25/directory26/directory27/directory28/directory29/directory30/directory31/directory32/directory33/directory34/directory35/directory36/directory37/directory38/directory39/directory40/directory41’: Directory not empty

Comment 2 Ravishankar N 2018-11-19 07:45:41 UTC
Being tracked at https://github.com/gluster/glusterfs/issues/502


Note You need to log in before you can comment on or make changes to this bug.