Bug 763359 (GLUSTER-1627)

Summary: touch/mkdir fails on some filenames
Product: [Community] GlusterFS Reporter: Lakshmipathi G <lakshmipathi>
Component: distributeAssignee: Amar Tumballi <amarts>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: 3.1-alphaCC: gluster-bugs, vijay, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTP Mount Type: All
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Lakshmipathi G 2010-09-17 06:48:22 UTC 
initially 2 dht cluster started and mounted through nfs.
Added new brick 3 and did a rebalance ,added another brick 4 ,
now running mkdir or touch following error msg- 
# mkdir o
mkdir: cannot create directory `o': Invalid argument

this happens with fuse or nfs mount.

client fuse  log
-------------
[2010-09-17 02:38:43.221891] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:38:46.767258] I [client-handshake.c:660:select_server_supported_programs] dhtaws-client-3: Using Program GlusterFS-3.1.0, Num (1298437), Version (310)
[2010-09-17 02:38:46.767369] I [client-handshake.c:660:select_server_supported_programs] dhtaws-client-1: Using Program GlusterFS-3.1.0, Num (1298437), Version (310)
[2010-09-17 02:38:46.769350] I [client-handshake.c:496:client_setvolume_cbk] dhtaws-client-3: Connected to 10.198.110.16:6971, attached to remote volume '/mnt/dir1'.
[2010-09-17 02:38:46.870458] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:38:46.870586] I [client-handshake.c:660:select_server_supported_programs] dhtaws-client-0: Using Program GlusterFS-3.1.0, Num (1298437), Version (310)
[2010-09-17 02:38:46.870709] I [client-handshake.c:496:client_setvolume_cbk] dhtaws-client-1: Connected to 10.192.141.187:6971, attached to remote volume '/mnt/dir1'.
[2010-09-17 02:38:46.972804] I [client-handshake.c:496:client_setvolume_cbk] dhtaws-client-0: Connected to 10.192.134.144:6971, attached to remote volume '/mnt/dir1'.
[2010-09-17 02:38:47.83332] I [fuse-bridge.c:2858:fuse_init] glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.13 kernel 7.8
[2010-09-17 02:38:50.749546] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:38:54.781532] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:38:58.758052] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:00.101807] W [fuse-bridge.c:180:fuse_entry_cbk] glusterfs-fuse: 34: MKDIR() /o => -1 (Invalid argument)
[2010-09-17 02:39:02.761807] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:06.794174] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:10.770832] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:14.774197] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:18.799571] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:22.783212] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:26.787092] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:30.795846] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:34.799724] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:38.803732] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:42.807987] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:46.830611] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:50.816748] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:54.820505] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:39:58.825136] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:40:02.852159] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:40:06.858256] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume
[2010-09-17 02:40:10.841778] E [client-handshake.c:730:client_query_portmap_cbk] dhtaws-client-2: failed to get the port number for remote subvolume