Changes between Version 3 and Version 4 of FAQ/CLVM


Ignore:
Timestamp:
05/21/11 17:10:09 (3 years ago)
Author:
digimer
Comment:

Fixed the last copy from the old wiki to work on the new Trac syntax.

Legend:

Unmodified
Added
Removed
Modified
  • FAQ/CLVM

    v3 v4  
    11= Cluster Logical Volume Management = 
    2  * [[#pvscan|Why doesn't pvscan find the volume I just created?]] 
    3  * [[#clvmd|Why didn't my clvmd start?]] 
    4  * [[#clvmd_ae|Can't I just use the LVM-Toolchain ae (Access Exclusive) option to protect data on my SAN?]] 
    5  * [[#clvmd_clustered|Why aren't changes to my logical volume being picked up by the rest of the cluster?]] 
    6  * [[FAQ/LockManager#dlm_timeout|clvmd locked up and I keep getting 'kernel: dlm: volumegroup: reply from 2 no lock' - how do I fix it?]] 
     2 * [#pvscan Why doesn't pvscan find the volume I just created?] 
     3 * [#clvmd Why didn't my clvmd start?] 
     4 * [#clvmd_ae Can't I just use the LVM-Toolchain ae (Access Exclusive) option to protect data on my SAN?] 
     5 * [#clvmd_clustered Why aren't changes to my logical volume being picked up by the rest of the cluster?] 
     6 * [/cluster/wiki/FAQ/LockManager#dlm_timeout clvmd locked up and I keep getting 'kernel: dlm: volumegroup: reply from 2 no lock' - how do I fix it?] 
    77 
    8 <<Anchor(pvscan)>> 
    9 ==== Why doesn't pvscan find the volume I just created? ==== 
     8==== Why doesn't pvscan find the volume I just created? ==== #pvscan 
    109{{{ 
    1110[root@taft-04 ~]# pvcreate /dev/sdb1 
     
    3029Try running "pvscan -vvvv | grep sdb" to make sure it's not filtered out. 
    3130 
    32 <<Anchor(clvmd)>> 
    33 ==== Why didn't my clvmd start? ==== 
     31==== Why didn't my clvmd start? ==== #clvmd 
    3432When I try to start clvmd, I get this message: 
    3533{{{ 
     
    4846cluster comes up but some of the nodes can't physically access the storage. 
    4947 
    50 <<Anchor(clvmd_ae)>> 
    51 ==== Can't I just use the LVM-Toolchain ae (Access Exclusive) option to protect data on my SAN? ==== 
     48==== Can't I just use the LVM-Toolchain ae (Access Exclusive) option to protect data on my SAN? ==== #clvmd_ae 
    5249No you can't.  Without some kind of cluster infrastructure, there's nothing to stop 
    5350the computers attached to your shared storage from corrupting and overwriting each other's data. 
     
    5552it has exclusive access. 
    5653 
    57 <<Anchor(clvmd_clustered)>> 
    58 ==== Why aren't changes to my logical volume being picked up by the rest of the cluster? ==== 
     54==== Why aren't changes to my logical volume being picked up by the rest of the cluster? ==== #clvmd_clustered 
    5955There's a little-known "clustering" flag for volume groups that should be set on when 
    6056a cluster uses a shared volume.  If that bit is not set, you can see strange lvm problems