Bug 384931
Summary: | RHEL5 cmirror tracker: unable to create a core log mirror | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Corey Marthaler <cmarthal> |
Component: | cmirror | Assignee: | Jonathan Earl Brassow <jbrassow> |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.0 | CC: | agk, dwysocha, jbrassow, mbroz, prockai |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-01-20 21:26:37 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Corey Marthaler
2007-11-15 16:21:49 UTC
A second time I tried this (after a reboot) the cmd hung with the storm of console messages: [root@taft-02 ~]# lvcreate -m 1 -n corelog --corelog -L 5G taft [HANG] [DM_CLOG_GET_RESYNC_WORK] to server: -3 device-mapper: dm-log-clustered: Unable to send cluster log request [DM_CLOG_GET_SYNC_COUNT] to server: -3 device-mapper: dm-log-clustered: Unable to send cluster log request [DM_CLOG_IS_REMOTE_RECOVERING] to server: -3 device-mapper: dm-log-clustered: Unable to send cluster log request [DM_CLOG_GET_RESYNC_WORK] to server: -3 device-mapper: dm-log-clustered: Unable to send cluster log request [DM_CLOG_GET_SYNC_COUNT] to server: -3 device-mapper: dm-log-clustered: Unable to send cluster log request [DM_CLOG_IS_REMOTE_RECOVERING] to server: -3 Nov 15 10:38:27 taft-02 kernel: device-mapper: dm-log-clustered: Unable to send cluster log request [DM_CLOG_GET3 For future reference, -3 means "No such process"... meaning the server probably segfaulted in your test. This means that you are probably able to grab a core file. Anyway, I believe I fixed this one while fixing 385001 (and others). Fix verified in cmirror-1.1.5-4.el5. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-0158.html |