Bug#913727: glusterfs-client: Could not mount glustertfs-server 3.12.11

2018-11-15 Thread Massimo Corà
Hi, On 11/15/18 9:40 AM, Patrick Matthäi wrote: Am 14.11.2018 um 17:32 schrieb Massimo Corà: Also 5.0 now uses ipv6 per default, so if you want to use ipv4 you have to set it up with a v4 address. I've disabled ipv6 on my box as on my lan it's not enabled. I suppose there should be a

Bug#913727: glusterfs-client: Could not mount glustertfs-server 3.12.11

2018-11-15 Thread Patrick Matthäi
Am 14.11.2018 um 17:32 schrieb Massimo Corà: > >> Also 5.0 now uses ipv6 per default, so if you want to use ipv4 you have >> to set it up with a v4 address. >> > > I've disabled ipv6 on my box as on my lan it's not enabled. > I suppose there should be a sort of fallback to ipv4 even if glusterfs

Bug#913727: glusterfs-client: Could not mount glustertfs-server 3.12.11

2018-11-14 Thread Massimo Corà
Hi, On 11/14/18 1:12 PM, Patrick Matthäi wrote: you shouldn't mix up client+server versions. well I've got working versions on Fedora 29 with glusterfs-client 5.0. Same server side 3.12.x Also 5.0 now uses ipv6 per default, so if you want to use ipv4 you have to set it up with a v4 address.

Bug#913727: glusterfs-client: Could not mount glustertfs-server 3.12.11

2018-11-14 Thread Patrick Matthäi
Hi, you shouldn't mix up client+server versions. Also 5.0 now uses ipv6 per default, so if you want to use ipv4 you have to set it up with a v4 address. Am 14.11.2018 um 12:32 schrieb Massimo Corà: > transport: attempt to load file > /usr/lib/x86_64-linux-gnu/glusterfs/5.0/rpc- >

Bug#913727: glusterfs-client: Could not mount glustertfs-server 3.12.11

2018-11-14 Thread Massimo Corà
Package: glusterfs-client Version: 5.0-1 Severity: normal Tags: ipv6 Dear Maintainer, I upgrade my linux box system, not I've got a glustefs-client 5. I cannot mount anymore glustefs server 3.x (which haven't changed nor have problems with 3.x clients). It seems it has some dns resolution