• Recent Articles

    LVM commands print "Volume Groups with the clustered attribute will be inaccessible."


    • I am unable to activate clustered volume groups even though clvmd is started

    connect() failed on local socket: No such file or directory
    Internal cluster locking initialisation failed.
    WARNING: Falling back to local file-based locking.
    Volume Groups with the clustered attribute will be inaccessible.
    Skipping clustered volume group VGgfs00


    • Make sure that the lvm and lvm-cluster packages are compatible.
    • The correct value for the option locking_type is not correctly set in /etc/lvm/lvm.conf can lead to "Volume Groups with the clustered attribute will be inaccessible".
    • For lvm-cluster to be properly configured ensure that the option locking_type is set to 3 in the global section of /etc/lvm/lvm.conf as noted in the article on HALVM. When using with GFS, or GFS2. Please note that if HALVM is used then the initrd image will need to be updated if the /etc/lvm/lvm.conf file changes.
    # grep locking_type /etc/lvm/lvm.conf | grep -v "#"
        locking_type = 1
    # lvmconf --enable-cluster
    # grep locking_type /etc/lvm/lvm.conf | grep -v "#"
        locking_type = 3
    # service clvmd restart
    • Ensure that clvmd has been started properly after the cluster node has joined the cluster.

    No comments