geo-rep status failing and snapshot creation failing on that particular volume, due to a lock held by one of the glusterd.

Solution In Progress - Updated -

Issue

We cannot do a geo-rep status on that particular volume, due to a lock held by one of the glusterd.

We restarted that glusterd and was able to see the status and stopped the geo-rep session for that particular volume.

When we try to create the snapshot, we encountered pre-verification failure on node 4.

After restarting that glusterd, the pre-verification failure moved to node 2 and then finally node 1.

After toggling the glusterds, we managed to creat a snapshot without the complaint that goe-rep is not stopped.

Unfortunately on a second snapshot create, we encountered another failure to to "changelog notify" failure on bricks in node 1.

Restarting the glusterd resolved that issue, and we managed to create snapshots successfully after that.

Environment

glusterfs 3.*

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content