On Fri, Aug 17, 2012 at 10:06 PM, Emmanuel Dreyfus <manu@xxxxxxxxxx> wrote:
Hi
How add-brick is supposed to be transparent for processes using the
glusterfs volume?
In my experiecne, add-brick on an inactive filesystems is completely
transparent. However, if there is some activity, during the operation, I
get transcient errors:
# cp -r /usr/local/src/glusterfs-33git ./
(here I add-brick)
cp: ./glusterfs-33git/.git/objects/f0: No such file or directory
In the FUSE operation log, I can see a lookup for the file that fails
with ENOENT, followed by MKDIR that also fails with ENOENT
Here is the glusterfs client log after I add the brick. Is that behavior
expected, or is there something missing I should implement in NetBSD
FUSE implemetation?
[2012-08-18 06:56:29.500791] I [rpc-clnt.c:1660:rpc_clnt_reconfig]
7-vndfs-client-0: changing port to 24010 (from 0)
[2012-08-18 06:56:29.501855] I [rpc-clnt.c:1660:rpc_clnt_reconfig]
7-vndfs-client-1: changing port to 24014 (from 0)
[2012-08-18 06:56:33.381571] I
[client-handshake.c:1636:select_server_supported_programs]
7-vndfs-client-0: Using Program GlusterFS 3.3git, Num (1298437),
Version (330)
[2012-08-18 06:56:33.381902] I
[client-handshake.c:1636:select_server_supported_programs]
7-vndfs-client-1: Using Program GlusterFS 3.3git, Num (1298437),
Version (330)
[2012-08-18 06:56:33.382405] I
[client-handshake.c:1433:client_setvolume_cbk] 7-vndfs-client-0:
Connected to 193.54.82.103:24010, attached to remote volume '
/export/vnd0a'.
[2012-08-18 06:56:33.382496] I
[client-handshake.c:1445:client_setvolume_cbk] 7-vndfs-client-0:
Server and Client lk-version numbers are not same, reopening the fds
[2012-08-18 06:56:33.383367] I
[client-handshake.c:453:client_set_lk_version_cbk] 7-vndfs-client-0:
Server lk version = 1
[2012-08-18 06:56:33.391422] I
[client-handshake.c:1433:client_setvolume_cbk] 7-vndfs-client-1:
Connected to 193.54.82.103:24014, attached to remote volume '
/export/vnd1a'.
[2012-08-18 06:56:33.391521] I
[client-handshake.c:1445:client_setvolume_cbk] 7-vndfs-client-1:
Server and Client lk-version numbers are not same, reopening the fds
[2012-08-18 06:56:33.432591] I [fuse-bridge.c:4193:fuse_graph_setup]
0-fuse: switched to graph 7
[2012-08-18 06:56:33.432828] I
[client-handshake.c:453:client_set_lk_version_cbk] 7-vndfs-client-1:
Server lk version = 1
[2012-08-18 06:56:33.442249] I [dht-layout.c:593:dht_layout_normalize]
7-vndfs-dht: found anomalies in /. holes=1 overlaps=0
[2012-08-18 06:56:33.453040] I [client.c:2151:notify] 6-vndfs-client-0:
current graph is no longer active, destroying rpc_client
[2012-08-18 06:56:33.454784] I [client.c:2090:client_rpc_notify]
6-vndfs-client-0: disconnected
[2012-08-18 06:56:33.466282] W [
[fuse-resolve.c:152:fuse_resolve_gfid_cbk] 0-fuse:
6a4a33a7-a37b-4a62-b63c-0e3f96226520: failed to resolve (Invalid
argument)
We need to investigate why there was EINVAL here. Either the resolution should have succeeded or returned ENOENT. The rest what follows is probably just cascaded effect of this.
Avati
[2012-08-18 06:56:33.466387] E [fuse-bridge.c:843:fuse_setattr_resume]
0-glusterfs-fuse: 2827: SETATTR 3032497708
(6a4a33a7-a37b-4a62-b63c-0e3f96226520) resolution failed
[2012-08-18 06:56:33.471578] W
[fuse-resolve.c:152:fuse_resolve_gfid_cbk] 0-fuse:
85f64202-a5f9-45a2-848d-0e1f4012d4b7: failed to resolve (Invalid
argument)
[2012-08-18 06:56:33.471704] E [fuse-bridge.c:352:fuse_lookup_resume]
0-fuse: failed to resolve path (null)
[2012-08-18 06:56:33.476630] W
[fuse-resolve.c:152:fuse_resolve_gfid_cbk] 0-fuse:
85f64202-a5f9-45a2-848d-0e1f4012d4b7: failed to resolve (Invalid
argument)
[2012-08-18 06:56:33.476728] E [fuse-bridge.c:352:fuse_lookup_resume]
0-fuse: failed to resolve path (null)
[2012-08-18 06:56:33.484311] W [
fuse-resolve.c:152:fuse_resolve_gfid_cbk] 0-fuse:
85f64202-a5f9-45a2-848d-0e1f4012d4b7: failed to resolve (Invalid
argument)
[2012-08-18 06:56:33.484414] E [fuse-bridge.c:1261:fuse_mkdir_resume]
0-glusterfs-fuse: MKDIR 3032485708 (
00000000-0000-0000-0000-000000000000/f0) resolution failed
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@xxxxxxxxxx
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
https://lists.nongnu.org/mailman/listinfo/gluster-devel
