Displaying 2 results from an estimated 2 matches for "takenduration".
2017 Oct 06
0
Gluster geo replication volume is faulty
...N/A
>
>
> Here is the output of the geo replication log file
> [root at gfs1 ~]# tail -n 100 $(gluster volume geo-replication gfsvol
> geo-rep-user at gfs4::gfsvol_rep config log-file)
> [2017-09-29 15:53:29.785386] I [master(/gfs/brick2/gv0):1860:syncjob]
> Syncer: Sync Time Takenduration=0.0357num_files=1job=3return_code=12
> [2017-09-29 15:53:29.785615] E [resource(/gfs/brick2/gv0):208:errlog]
> Popen: command returned errorcmd=rsync -aR0 --inplace --files-from=-
> --super --stats --numeric-ids --no-implied-dirs --existing --xattrs
> --acls . -e ssh -oPasswordAuthen...
2017 Sep 29
1
Gluster geo replication volume is faulty
I am trying to get up geo replication between two gluster volumes
I have set up two replica 2 arbiter 1 volumes with 9 bricks
[root at gfs1 ~]# gluster volume info
Volume Name: gfsvol
Type: Distributed-Replicate
Volume ID: c2fb4365-480b-4d37-8c7d-c3046bca7306
Status: Started
Snapshot Count: 0
Number of Bricks: 3 x (2 + 1) = 9
Transport-type: tcp
Bricks:
Brick1: gfs2:/gfs/brick1/gv0
Brick2: