[Bugs] [Bug 1668989] Unable to delete directories that contain linkto files that point to itself.

bugzilla at redhat.com bugzilla at redhat.com
Tue Feb 26 11:45:35 UTC 2019


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

Sayalee <saraut at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ON_QA                       |VERIFIED



--- Comment #6 from Sayalee <saraut at redhat.com> ---

I have performed the following steps (as mentioned in #Description) and did NOT
hit the issue on 3.12.2-45 build:

  1) Create a pure distribute volume with two bricks and start it.
  2) FUSE mount the volume on a client node using:
   # mount -t glusterfs -s <ip-address>:/<volname> /mnt/<mnt-dir>
  3) On the mount point do following operations:
   # cd /mnt/<mnt-dir>
   # mkdir -p dir0/dir1/dir2
   # cd dir0/dir1/dir2
   # for i in {1..100}; do echo "Test file" > tfile-$i; done
   # for i in {1..100}; do mv tfile-$i ntfile-$i; done
  4) Start remove-brick operation on the volume using:
   # gluster v remove-brick <vol-name> brick2 start
  5) Check the remove brick status using:
   # gluster v remove-brick <vol-name> brick2 status
  6) When the remove-brick status is shown as "complete" for all the nodes,
stop the remove-brick operation using:
   # gluster v remove-brick <vol-name> brick2 stop
  7) Go to brick2 and perform lookup on the files. (only linkto files must be
present and all should point to "vol_name-client-0")
  8) Now change the linkto xattr value for every file in brick2 to point to
itself (in this case "vol_name-client-1", also make sure the string is null
terminated)
   # setfattr -n trusted.glusterfs.dht.linkto -v 0x74766f6c2d636c69656e742d3100
/bricks/brick2/<vol-brick>/dir0/dir1/dir2/ntfile-*
  9) Now from the mount-point perform following operations in order to delete
the directory:
   # cd /mnt/<mnt-dir>
   # rm -rf *

Also covered the regression cases as mentioned in the test plan shared in
#comment5

Hence moving this bug to verified.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Bugs mailing list