[Bugs] [Bug 1140818] New: symlink changes to directory, that reappears on removal

[bugzilla at redhat.com]

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

            Bug ID: 1140818
           Summary: symlink changes to directory, that reappears on
                    removal
           Product: GlusterFS
           Version: 3.5.2
         Component: core
          Severity: high
          Assignee: gluster-bugs at redhat.com
          Reporter: aa at evp.lt
                CC: bugs at gluster.org



Description of problem:

two replicated bricks provides volume www, mounted on client node as /var/www
via fuse.glusterfs (glusterfs defaults,_netdev). rsync deploys about 9300 php
files to directory /var/www/backend/releases/<new-time-stamp> on client node,
and then relinks (symlink) /var/www/backend/current as this uploaded
<new-time-stamp> dir like this:

cd /var/www/backend && ln -s releases/20140911151733
/var/www/backend/current_tmp && mv -Tf /var/www/backend/current_tmp
/var/www/backend/current

please note that symlink 'current' already existed and pointed to another dir
in /var/www/backend/releases/ when command above was run.

What happens is that instead of getting new symlink 'current' pointing to newly
uploaded source, we get directory 'current' that cannot be deleted - 'rm -fr
current' succeeds, but it reappears second later. The only way to remove
'current' is to shut down all nodes, stop glusterfs[d] and remove directory on
bricks themselves. This is critical as we have to kill whole cluster.

Version-Release number of selected component (if applicable):
3.5.2-ubuntu1~trusty1, amd64

Actual results:
'current' appears as directory, cannot be deleted

Expected results:
'current' should appear as link that points to new directory

Additional info:
all nodes are ubuntu 14.04LTS amd64 VM's, having at least 1GB of free memory
left. Two mirrored bricks are glusterfs v3.5.2. Four client nodes mounts volume
via NFS, deployment node (where rsync and commands below runs) mounts volume as
glusterfs.

full source deployment script that causes problem:
  * executing `deploy:copy_remote_cache'
  * executing "rsync -az --delete /var/www/backend/shared/cached-copy/
/var/www/backend/releases/20140911151733/"
  * executing "chmod -R g+w /var/www/backend/releases/20140911151733"
  * executing "sh -c 'if [ -d
/var/www/backend/releases/20140911151733/var/cache ] ; then rm -rf
/var/www/backend/releases/20140911151733/var/cache; fi'"
  * executing "sh -c 'mkdir -p
/var/www/backend/releases/20140911151733/var/cache && chmod -R 0777
/var/www/backend/releases/20140911151733/var/cache'"
  * executing "chmod -R g+w /var/www/backend/releases/20140911151733/var/cache"
  * executing "find /var/www/backend/releases/20140911151733/web/css
/var/www/backend/releases/20140911151733/web/images
/var/www/backend/releases/20140911151733/web/js -exec touch -t 201409111521.41
{} ';' &> /dev/null || true"
  * executing "cd /var/www/backend && ln -s releases/20140911151733
/var/www/backend/current_tmp && mv -Tf /var/www/backend/current_tmp
/var/www/backend/current"

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