Bug 506592 - lvm2-cluster lacks Requires: cman
lvm2-cluster lacks Requires: cman
Product: Fedora
Classification: Fedora
Component: lvm2-cluster (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Fabio Massimo Di Nitto
Fedora Extras Quality Assurance
Depends On:
Blocks: 557662
  Show dependency treegraph
Reported: 2009-06-17 17:05 EDT by Jan "Yenya" Kasprzak
Modified: 2010-02-17 17:27 EST (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 557662 (view as bug list)
Last Closed: 2010-01-22 01:08:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan "Yenya" Kasprzak 2009-06-17 17:05:06 EDT
Description of problem:
When trying to start clvmd, it fails after several seconds delay with the following message:

clvmd could not connect to cluster manager
Consult syslog for more information

And in /var/log/messages there is the following line:

Jun 17 22:49:53 yuki1 clvmd: Unable to create lockspace for CLVM: No such file or directory

Running clvmd under "strace -f" shows that the last ENOENT before the above message is sent to the syslog is this:

1580  stat("/dev/misc/dlm-control", 0x7fff8a7d6ee0) = -1 ENOENT (No such file or directory)

On my system (a freshly installed F11) the DLM devices (dlm-control, dlm-monitor, and dlm_plock) are directly under /dev, not under /dev/misc.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. have a system with lvm2-cluster installed and corosync up and running.
2. modprobe dlm
3. strace -f -o /tmp/clvmd.strace clvmd
Actual results:
clvmd dies with the above messages, in strace it can be seen that it tries to open /dev/misc/dlm-control

Expected results:
It should open /dev/dlm-control (or alternatively, udev should create /dev/misc/dlm-control)

Additional info:
I am new to clustered lvm, so I am not sure if whether I am missing something or not. I have tried to do a band-aid fix:

mkdir /dev/misc
cd /dev/misc
ln -s ../dlm* .

Then clvmd at least dies immediately, and with different messages:

Jun 17 22:58:00 yuki1 kernel: dlm: no local IP address has been set
Jun 17 22:58:00 yuki1 clvmd: Unable to create lockspace for CLVM: Transport endpoint is not connected
Jun 17 22:58:00 yuki1 kernel: dlm: cannot start dlm lowcomms -107
Comment 1 Milan Broz 2009-06-17 17:29:14 EDT
I think you need to install and run cman (which at least in rawhide contains udev rules to create this node). 

Anyway, it is cluster-lib code here which open dlm-control, reassigning to cluster package (clvmd only uses it).
Comment 2 Fabio Massimo Di Nitto 2009-06-17 17:37:58 EDT
I am not sure this is a bug...

is cman running at all?

what's the output of cman_tool status and cman_tool nodes?

can you provide cluster.conf?

dlm needs to be running and configured via cman and it doesn't look like from the errors in dmesg.

Comment 3 Jan "Yenya" Kasprzak 2009-06-17 17:56:36 EDT
OK, then the bug is that lvm2-cluster lacks "Requires: cman", if it cannot be run without cman.

As I said, I am pretty new to clvm. So I have installed lvm2-cluster and looked at its dependences. In F11, it brought only corosync in, so I have tried at least to configure and run corosync. I had no idea that cman is required to run clustered lvm.

cman-3.0.0-15.rc1.fc11.x86_64 indeed contains correct udev rules for /dev/misc/dlm*.

Changing the component back to lvm2-cluster and editing the title of the bug.
Comment 4 Christine Caulfield 2009-06-18 02:53:18 EDT
Yes, lvm2-cluster needs to depend on cman, because cman provides the DLM userspace files that it will use. Also the DLM currently depends on cman to run in the first place, so anything that depends on DLM (as clvmd does) will also require cman.

This dependency will be lifted in the future.

Note You need to log in before you can comment on or make changes to this bug.