Re: [Gluster-users] [rhgs-devel] Gluster meetup: India

2018-12-17 Thread Amye Scavarda
This is great!
Want to put it on the Gluster blog?
- amye

On Sun, Dec 16, 2018 at 11:19 PM Sunny Kumar  wrote:

> Hello folks,
>
> Gluster meetup is back and we will be hosting it in our office
> (Redhat-BLR-IN).
> Please find the agenda and location detail here [1] and plan accordingly.
>
> The highlight of this event will be Gluster in container world,
> involving discussion around GCS (Gluster Container Storage) [2]. You
> can try out latest GCS release here[3] and provide feedback.
>
> Note:
>  * RSVP as YES if attending, this will help us to organize the
> facilities better.
>
> If you have any question, please reach out to me or comment on the
> event page [4].
>
> 1. http://meetu.ps/e/FZ9GH/zB8xy/f
> 2. https://github.com/gluster/gcs.
> 3.
> https://lists.gluster.org/pipermail/gluster-users/2018-December/035457.html
> 4. https://www.meetup.com/glusterfs-India/events/255792144/
>
> - Sunny
>
>

-- 
Amye Scavarda | a...@redhat.com | Gluster Community Lead
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] File renaming not geo-replicated

2018-12-17 Thread Sunny Kumar
Hi Arnaud,

Can you please share geo-replication log for master and mount log form slave.

- Sunny

On Mon, Dec 17, 2018 at 4:09 PM Arnaud Launay  wrote:
>
> Hello Sunny,
>
> Thanks for the feedback.
>
> Le Mon, Dec 17, 2018 at 03:59:07PM +0530, Sunny Kumar a écrit:
> > This is how it supposed to work on any file system including GlusterFS.
> > root@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@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
>
> This is /not/ my problem, that is what I see (and want) on prod01
> and prod02 (basic replication), but on test (georep), foo.txt
> still exists and bar.txt is never present: the rename never takes place.
>
> Arnaud.
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] File renaming not geo-replicated

2018-12-17 Thread Arnaud Launay
Hello Sunny,

Thanks for the feedback.

Le Mon, Dec 17, 2018 at 03:59:07PM +0530, Sunny Kumar a écrit:
> This is how it supposed to work on any file system including GlusterFS.
> root@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@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

This is /not/ my problem, that is what I see (and want) on prod01
and prod02 (basic replication), but on test (georep), foo.txt
still exists and bar.txt is never present: the rename never takes place.

Arnaud.


signature.asc
Description: PGP signature
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] File renaming not geo-replicated

2018-12-17 Thread Sunny Kumar
Hi Arnaud,

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

root@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@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  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@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@prod01:/srv/www# touch foo.txt && mv foo.txt bar.txt
> > root@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@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@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@gluster.org
> > https://lists.gluster.org/mailman/listinfo/gluster-users
>
> Arnaud.
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] File renaming not geo-replicated

2018-12-17 Thread Arnaud Launay
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@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@prod01:/srv/www# touch foo.txt && mv foo.txt bar.txt
> root@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@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@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@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users

Arnaud.


signature.asc
Description: PGP signature
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users