[Linux-cluster] cmirror leg failure: dmeventd dies
Robert Clark
cluster at defuturo.co.uk
Wed Jun 13 16:31:10 UTC 2007
I've recently upgraded from RHEL4U4 to RHEL4U5 in order to use the new
cmirror package instead of one I was building myself from CVS.
Now, when I fail one of the PVs, the mirrored LV isn't converted to
linear. Instead, dmeventd dies like this:
3377 send(6, "<15>Jun 12 16:50:34 lvm[3371]: Loaded external locking library liblvm2clusterlock.so", 84, MSG_NOSIGNAL) = 84
3377 socket(PF_FILE, SOCK_STREAM, 0) = 7
3377 connect(7, {sa_family=AF_FILE, path=@clvmd}, 110) = 0
3377 time(NULL) = 1181663434
3377 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1323, ...}) = 0
3377 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1323, ...}) = 0
3377 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1323, ...}) = 0
3377 send(6, "<15>Jun 12 16:50:34 lvm[3371]: Finding volume group \"lvm_test1\"", 63, MSG_NOSIGNAL) = 63
3377 stat64("/proc/lvm/VGs/lvm_test1", 0xf6fa6340) = -1 ENOENT (No such file or directory)
3377 rt_sigprocmask(SIG_SETMASK, ~[RTMIN RT_1], ~[HUP INT QUIT KILL TERM STOP RTMIN RT_1], 8) = 0
3377 writev(2, [{"<program name unknown>", 22}, {": ", 2}, {"symbol lookup error", 19}, {": ", 2}, {"/usr/lib/liblvm2clusterlock.so", 30}, {": ", 2}, {"undefined symbol: print_log", 27}, {"", 0}, {"", 0}, {"\n", 1}], 10) = 105
3377 exit_group(127) = ?
and logs this:
Jun 12 13:43:57 kiwano dmeventd[3371]: dmeventd ready for processing.
Jun 12 13:43:57 kiwano dmeventd[3371]: Monitoring mirror device lvm_test1-var for events
Jun 12 13:44:08 kiwano lvm[3371]: lvm_test1-var is now in-sync
Jun 12 16:50:33 kiwano lvm[3371]: Mirror device, 253:5, has failed.
Jun 12 16:50:33 kiwano lvm[3371]: Device failure in lvm_test1-var
Jun 12 16:50:33 kiwano lvm[3371]: WARNING: dev_open(/etc/lvm/lvm.conf) called while suspended
The "undefined symbol: print_log" error looks pretty fatal and "ldd
-r /usr/lib/liblvm2clusterlock.so" reports it too, though it does the
same on working clusters and a FC6 box as well.
Can anyone suggest how to debug this?
Thanks,
Robert
More information about the Linux-cluster
mailing list