[Gluster-users] File renaming not geo-replicated

[Sunny Kumar]

Hi Arnaud,

This is how it supposed to work on any file system including GlusterFS.

root at prod01:/srv/www# touch foo.txt && mv foo.txt bar.txt

Here foo.txt is created and then it is renamed to bar.txt

root at prod01:/srv/www# ls -l foo.txt bar.txt
ls: cannot access 'foo.txt': No such file or directory

-- SO this is correct foo should not exist as it is renamed to bar.
-rw-rw-r-- 1 root root 0 Dec 10 12:34 bar.txt

- Sunny
On Mon, Dec 17, 2018 at 3:36 PM Arnaud Launay <asl at launay.org> wrote:
>
> Hello,
>
> Should I open a bug somewhere for hoping to get an answer ?
>
> Thanks,
> Arnaud.
>
> Le Mon, Dec 10, 2018 at 01:15:30PM +0100, Arnaud Launay a écrit:
> > We have a simple glusterfs setup, with one volume replicated on two
> > servers, and on a third one using georeplication.
> >
> > Environment:
> > - Debian 9 stretch uptodate
> > - gluster repository:
> > deb [arch=amd64] https://download.gluster.org/pub/gluster/glusterfs/4.1/LATEST/Debian/stretch/amd64/apt stretch main
> >
> > Last version:
> >
> > root at prod01:~# gluster --version
> > glusterfs 4.1.6
> > Repository revision: git://git.gluster.org/glusterfs.git
> >
> > (same on all three servers)
> >
> > Basic brick, lvm-mapper with an XFS and ACL filesystem:
> > /dev/mapper/data-glusterwww on /var/lib/glusterbricks/gbrick1 type xfs (rw,noatime,nodiratime,attr2,inode64,noquota)
> >
> > Then mounted locally via NFS (slightly quicker access time):
> > 127.0.0.1:/www0 on /srv/www type nfs (rw,noatime,nodiratime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=127.0.0.1,mountvers=3,mountport=38465,mountproto=tcp,local_lock=none,addr=127.0.0.1)
> >
> >
> >
> > We have a problem with the georep one, when renaming a file:
> >
> > root at prod01:/srv/www# touch foo.txt && mv foo.txt bar.txt
> > root at prod01:/srv/www# ls -l foo.txt bar.txt
> > ls: cannot access 'foo.txt': No such file or directory
> > -rw-rw-r-- 1 root root 0 Dec 10 12:34 bar.txt
> >
> > It's perfectly replicated on the second one:
> >
> > root at prod02:/srv/www# ls -l foo.txt bar.txt
> > ls: cannot access 'foo.txt': No such file or directory
> > -rw-rw-r-- 1 root root 0 Dec 10 12:34 bar.txt
> >
> >
> >
> > But the georeplicated one does not match:
> >
> > root at test:/srv/mirror-prod-www# ls -l foo.txt bar.txt
> > ls: cannot access 'bar.txt': No such file or directory
> > -rw-rw-r-- 2 root root 0 Dec 10 12:34 foo.txt
> >
> >
> >
> > The touched file (still) exists, but the mv has not been passed along.
> >
> > We tried multiple things, including deleting the georeplicated brick and
> > creating it again from scratch, but the problem is still present.
> >
> >
> > We saw that this has been the object of a few bugs in the past, but they seem
> > to have been corrected. Any idea ?
> >
> >       Arnaud.
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users at gluster.org
> > https://lists.gluster.org/mailman/listinfo/gluster-users
>
>         Arnaud.
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users