[Bugs] [Bug 1387494] Files not deleted from data brick after deletion from the mount point.

[bugzilla at redhat.com]

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

Ravishankar N <ravishankar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(ksandha at redhat.co
                   |                            |m)



--- Comment #6 from Ravishankar N <ravishankar at redhat.com> ---
RCA:
The script creates 500MB files and fills up the 2 data bricks midway. Though
the subsequent mkdir/creates fail on the mount with ENOTCONN, the arbiter brick
still gets filled up with the dirs and 0-byte files. Thus the arbiter has more
files and dirs than the data bricks. Also, since the "cd .." in the script gets
ENOTCONN now (since fop succeeded only on arbiter) , files/dirs are created in
a haphazard manner in arbiter (i.e. not following the same order as the script
intended it to be).

Now when brick2 is brought down and rm -rf is done from the mount, the readdir
is served from brick1. The dentries present in b1 and b3 are deleted. But when
rmdir comes on the parent, it fails on the arbiter brick with ENOTEMPY because
it has extra files/dirs. Thus at the end of rm -rf, the dirs/files are still
present in the arbiter.

Karan, I think there is a typo in the BZ description. It should read 'Files not
deleted from the arbiter brick..'. Could you confirm and change it?

-- 
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=WIIlNn75i7&a=cc_unsubscribe