Why do I get locking errors or "connection refused" errors when running LVM commands on a GFS filesystem after expanding a volume group?

Updated -

Release Found :Red Hat Enterprise Linux 4

Description:

There is a known issue in clvmd where the daemon does not properly update its cache after the underlying storage of a volume group is changed.

For example, a new physical volume is created, and then it is added to a volume group using the vgextend command. Fro...

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.