Displaying 4 results from an estimated 4 matches for "dht_selfheal_layout_new_directori".
Did you mean:
dht_selfheal_layout_new_directory
2013 Jun 17
0
gluster client timeouts / found conflict
Hi list
Recently I've experienced more and more input/output errors from my most
write heavy gluster filesystem.
The logfile on the gluster servers show nothing, but the client(s) that get
the input/output errors (and timeouts) will as far as I can tell get errors
such as :
[2013-06-14 15:55:56] W [fuse-bridge.c:493:fuse_entry_cbk] glusterfs-fuse:
LOOKUP(/369/60702093) inode (ptr=0x1efd440,
2017 Sep 20
1
"Input/output error" on mkdir for PPC64 based client
I put the share into debug mode and then repeated the process from a ppc64
client and an x86 client. Weirdly the client logs were almost identical.
Here's the ppc64 gluster client log of attempting to create a folder...
-------------
[2017-09-20 13:34:23.344321] D
[rpc-clnt-ping.c:93:rpc_clnt_remove_ping_timer_locked] (-->
2017 Sep 20
0
"Input/output error" on mkdir for PPC64 based client
Looks like it is an issue with architecture compatibility in RPC layer (ie,
with XDRs and how it is used). Just glance the logs of the client process
where you saw the errors, which could give some hints. If you don't
understand the logs, share them, so we will try to look into it.
-Amar
On Wed, Sep 20, 2017 at 2:40 AM, Walter Deignan <WDeignan at uline.com> wrote:
> I recently
2017 Sep 19
3
"Input/output error" on mkdir for PPC64 based client
I recently compiled the 3.10-5 client from source on a few PPC64 systems
running RHEL 7.3. They are mounting a Gluster volume which is hosted on
more traditional x86 servers.
Everything seems to be working properly except for creating new
directories from the PPC64 clients. The mkdir command gives a
"Input/output error" and for the first few minutes the new directory is