<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font face="Calibri">Hi,<br>
<br>
we have a setup with a 2 node gluster replication cluster where
the volume is exported through the gluster build-in nfs service.<br>
This volume is also replicated to a secondary site with geo-replication.<br>
<br>
The problem is, that when clients are writing files larger than
10M, once every time the write gets aborted with a input/output
error. At that moment, following lines appear in the
gluster/bricks log:<br>
<br>
[2013-07-01 12:41:39.800465] E [posix.c:2128:posix_writev]
0-<vol>-posix: write failed: offset 1069056, Bad file
descriptor<br>
[2013-07-01 12:41:39.800510] I
[server3_1-fops.c:1414:server_writev_cbk] 0-<vol>-server:
114834: WRITEV -2 (8e01b426-11dd-4147-9e5c-9256ca118be7) ==> -1
(Bad file descriptor)<br>
<br>
When geo-replication is stopped, these errors do not occur, so I
suspect this is some kind of locking issue between the integrated
nfs server en the crawler for the geo-rep.<br>
<br>
Anybody any ideas how to circumvent this?<br>
<br>
Version information of the gluster servers:<br>
<br>
CentOS release 6.4 (Final)<br>
glusterfs-3.3.1-1.el6.x86_64<br>
glusterfs-server-3.3.1-1.el6.x86_64<br>
glusterfs-fuse-3.3.1-1.el6.x86_64<br>
glusterfs-geo-replication-3.3.1-1.el6.x86_64<br>
<br>
regards,<br>
Sam</font><br>
</body>
</html>