That's unfortunately not possible in my case as the clients are K8s worker
nodes. The gluster client version is tied to the Kuberntes release/deployer
- Rancher in my case.
Disabling ctime "gluster volume set $volname ctime off" fixed the mounting
issue.
On Thu, Jan 30, 2020 at 4:16 AM Mahdi Ad
Hello,
We had a similar issue when we upgraded one of our clusters to 6.5 and
clients were running 4.1.5 and 4.1.9, both crashed after few seconds of
mounting, we did not dig into the issue instead, we upgraded the clients to
6.5 and it worked fine.
On Tue, Jan 28, 2020 at 1:35 AM Laurent Dumont
After some more digging, it seems I'm hitting the following bug -
https://github.com/gluster/glusterfs/issues/658
On Mon, Jan 27, 2020 at 4:23 PM Laurent Dumont
wrote:
> Hi everyone,
>
> Small question. I'm trying to mount a Gluster volume (server is at 6.7)
> and the client is at 4.1.5. I'm see
Hi everyone,
Small question. I'm trying to mount a Gluster volume (server is at 6.7) and
the client is at 4.1.5. I'm seeing the mount start on the client but it
looks like the client crashes and is left in a strange state. Is there any
inherent compatibility issues between the two versions? Is 4.1
