Thanks for the command, this is the result of that ls:
lrwxrwxrwx 1 root root 60 Jul 26 16:12
/data/cloud-pro/brick/.glusterfs/f7/eb/f7eb9d21-d39a-4dd6-941c-46d430e18aa2 ->
../../aa/63/aa63d3f7-656e-4e92-a016-a878714e89f8/Booking
On Friday, September 16, 2016 11:58 AM, Aravinda
We can check in brick backend.
ls -ld $BRICK_ROOT/.glusterfs/f7/eb/f7eb9d21-d39a-4dd6-941c-46d430e18aa2
regards
Aravinda
On Thursday 15 September 2016 09:12 PM, ML mail wrote:
So I ran a on my master a "find /mybrick -name 'File 2016.xlsx'" and got the
following two entries:
355235 19
So I ran a on my master a "find /mybrick -name 'File 2016.xlsx'" and got the
following two entries:
355235 19 drwxr-xr-x 3 www-data www-data3 Sep 15 12:48
./data/username/files_encryption/keys/files/Dir/File\ 2016.xlsx
355234 56 -rw-r--r-- 2 www-data www-data44308 Sep 15
Thanks for the logs from Master. Below error says directory not empty
but names looks like they are files. Please confirm from Master Volume
that path is directory or file.
[2016-09-13 19:30:57.475649] W [fuse-bridge.c:1787:fuse_rename_cbk]
0-glusterfs-fuse: 25:
As requested you will find below the last few 100 lines of the geo-rep log file
from the master node.
FILE:
/var/log/glusterfs/geo-replication/cloud-pro/ssh%3A%2F%2Froot%40192.168.20.107%3Agluster%3A%2F%2F127.0.0.1%3Acloud-pro-geo.log
[2016-09-13 19:39:48.686060] I
Thanks, but couldn't find one log file output. To get the log file path
gluster volume geo-replication :: config
log_file
regards
Aravinda
On Wednesday 14 September 2016 12:02 PM, ML mail wrote:
Dear Aravinda,
As requested I have attached within this mail a file containing the last
Dear Aravinda,
As requested I have attached within this mail a file containing the last
100-300 lines of the three files located in the requested directory on the
master node.
Let me know if you did not receive the file, I am not sure it is possible to
attach files on this mailing list.
Please share the logs from Master node which is
Faulty(/var/log/glusterfs/geo-replication/__/*.log)
regards
Aravinda
On Wednesday 14 September 2016 01:10 AM, ML mail wrote:
Hi,
I just discovered that one of my replicated glusterfs volumes is not being
geo-replicated to my slave node (STATUS
Hi,
I just discovered that one of my replicated glusterfs volumes is not being
geo-replicated to my slave node (STATUS Faulty). The log file on the geo-rep
slave node indicates an error with a directory which seems not to be empty.
Below you will find the full log entry for this problem which
