Displaying 3 results from an estimated 3 matches for "tempdir3".
Did you mean:
tempdir
2017 Sep 20
1
"Input/output error" on mkdir for PPC64 based client
...event already removed
[2017-09-20 13:34:23.346070] D [MSGID: 0]
[dht-common.c:1002:dht_revalidate_cbk] 0-gv0-dht: revalidate lookup of /
returned with op_ret 0 [Structure needs cleaning]
[2017-09-20 13:34:23.347612] D [MSGID: 0] [dht-common.c:2699:dht_lookup]
0-gv0-dht: Calling fresh lookup for /tempdir3 on gv0-replicate-0
[2017-09-20 13:34:23.348013] D [MSGID: 0]
[client-rpc-fops.c:2936:client3_3_lookup_cbk] 0-stack-trace:
stack-address: 0x3fff88001080, gv0-client-1 returned -1 error: No such
file or directory [No such file or directory]
[2017-09-20 13:34:23.348013] D [MSGID: 0]
[client-rpc-fo...
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