Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 305290 Details for
Bug 446255
RHEL5 cmirror tracker: data corruption after restoring failed log device on three mirrors
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
log from taft-01
taft-01.log (text/plain), 13.74 KB, created by
Corey Marthaler
on 2008-05-13 19:56:03 UTC
(
hide
)
Description:
log from taft-01
Filename:
MIME Type:
Creator:
Corey Marthaler
Created:
2008-05-13 19:56:03 UTC
Size:
13.74 KB
patch
obsolete
>May 13 12:38:39 taft-01 qarshd[18287]: Running cmdline: echo running > /sys/block/sdh/device/state >May 13 12:38:39 taft-01 xinetd[6223]: EXIT: qarsh status=0 pid=18287 duration=0(sec) >May 13 12:38:44 taft-01 lvm[6767]: No longer monitoring mirror device helter_skelter-syncd_log_2legs_1 for events >May 13 12:38:48 taft-01 kernel: device-mapper: dm-log-clustered: [aPZNi3wq] Request timed out: [DM_CLOG_GET_RESYNC_WORK/2027513] - retrying >May 13 12:39:03 taft-01 kernel: device-mapper: dm-log-clustered: [aPZNi3wq] Request timed out: [DM_CLOG_CLEAR_REGION/2027741] - retrying >May 13 12:39:03 taft-01 clogd[6683]: [aPZNi3wq] Unable to send DM_CLOG_CLEAR_REGION to cluster: No such file or directory >May 13 12:39:03 taft-01 clogd[6683]: Bad callback on local/4 >May 13 12:39:03 taft-01 kernel: device-mapper: dm-log-clustered: [aPZNi3wq] Server error while processing request [DM_CLOG_CLEAR_REGION]: -2 >May 13 12:39:03 taft-01 clogd[6683]: [aPZNi3wq] Unable to send DM_CLOG_CLEAR_REGION to cluster: No such file or directory >May 13 12:39:03 taft-01 clogd[6683]: Bad callback on local/4 >May 13 12:39:03 taft-01 kernel: device-mapper: dm-log-clustered: [aPZNi3wq] Server error while processing request [DM_CLOG_CLEAR_REGION]: -2 >May 13 12:39:03 taft-01 lvm[6767]: Monitoring mirror device helter_skelter-syncd_log_2legs_1 for events >May 13 12:39:03 taft-01 lvm[6767]: helter_skelter-syncd_log_2legs_1 is now in-sync >May 13 12:39:04 taft-01 clogd[6683]: Invalid request_type >May 13 12:39:15 taft-01 lvm[6767]: No longer monitoring mirror device helter_skelter-syncd_log_2legs_2 for events >May 13 12:39:19 taft-01 kernel: device-mapper: dm-log-clustered: [e1WLmXTb] Request timed out: [DM_CLOG_IN_SYNC/2027805] - retrying >May 13 12:39:34 taft-01 kernel: device-mapper: dm-log-clustered: [e1WLmXTb] Request timed out: [DM_CLOG_CLEAR_REGION/2028245] - retrying >May 13 12:39:34 taft-01 clogd[6683]: [e1WLmXTb] Unable to send DM_CLOG_CLEAR_REGION to cluster: No such file or directory >May 13 12:39:34 taft-01 clogd[6683]: Bad callback on local/4 >May 13 12:39:34 taft-01 kernel: device-mapper: dm-log-clustered: [e1WLmXTb] Server error while processing request [DM_CLOG_CLEAR_REGION]: -2 >May 13 12:39:34 taft-01 clogd[6683]: [e1WLmXTb] Unable to send DM_CLOG_CLEAR_REGION to cluster: No such file or directory >May 13 12:39:34 taft-01 clogd[6683]: Bad callback on local/4 >May 13 12:39:34 taft-01 kernel: device-mapper: dm-log-clustered: [e1WLmXTb] Server error while processing request [DM_CLOG_CLEAR_REGION]: -2 >May 13 12:39:34 taft-01 lvm[6767]: Monitoring mirror device helter_skelter-syncd_log_2legs_2 for events >May 13 12:39:34 taft-01 lvm[6767]: helter_skelter-syncd_log_2legs_2 is now in-sync >May 13 12:39:34 taft-01 clogd[6683]: Invalid request_type >May 13 12:39:35 taft-01 lvm[6767]: No longer monitoring mirror device helter_skelter-syncd_log_2legs_3 for events >May 13 12:39:49 taft-01 kernel: device-mapper: dm-log-clustered: [j9j2Tbjg] Request timed out: [DM_CLOG_IN_SYNC/2028318] - retrying >May 13 12:39:49 taft-01 clogd[6683]: [j9j2Tbjg] Attempt to send request to cluster while CPG not valid: request = DM_CLOG_FLUSH >May 13 12:39:49 taft-01 clogd[6683]: [j9j2Tbjg] Unable to send DM_CLOG_FLUSH to cluster: Invalid argument >May 13 12:39:49 taft-01 clogd[6683]: Bad callback on local/4 >May 13 12:39:49 taft-01 clogd[6683]: [j9j2Tbjg] Unable to send DM_CLOG_CLEAR_REGION to cluster: No such file or directory >May 13 12:39:49 taft-01 clogd[6683]: Bad callback on local/4 >May 13 12:39:49 taft-01 kernel: device-mapper: dm-log-clustered: [j9j2Tbjg] Server error while processing request [DM_CLOG_FLUSH]: -22 >May 13 12:39:49 taft-01 kernel: device-mapper: dm-log-clustered: [j9j2Tbjg] Server error while processing request [DM_CLOG_CLEAR_REGION]: -2 >May 13 12:39:49 taft-01 lvm[6767]: Monitoring mirror device helter_skelter-syncd_log_2legs_3 for events >May 13 12:39:49 taft-01 lvm[6767]: helter_skelter-syncd_log_2legs_3 is now in-sync >May 13 12:40:03 taft-01 xinetd[6223]: START: qarsh pid=18507 from=10.15.80.47 >May 13 12:40:03 taft-01 qarshd[18507]: Talking to peer 10.15.80.47:44843 >May 13 12:40:03 taft-01 qarshd[18507]: Running cmdline: lvs -o copy_percent --noheadings helter_skelter/syncd_log_2legs_1 >May 13 12:40:03 taft-01 xinetd[6223]: EXIT: qarsh status=0 pid=18507 duration=0(sec) >May 13 12:40:03 taft-01 xinetd[6223]: START: qarsh pid=18510 from=10.15.80.47 >May 13 12:40:03 taft-01 qarshd[18510]: Talking to peer 10.15.80.47:44844 >May 13 12:40:03 taft-01 qarshd[18510]: Running cmdline: lvs -o copy_percent --noheadings helter_skelter/syncd_log_2legs_2 >May 13 12:40:03 taft-01 xinetd[6223]: EXIT: qarsh status=0 pid=18510 duration=0(sec) >May 13 12:40:03 taft-01 xinetd[6223]: START: qarsh pid=18513 from=10.15.80.47 >May 13 12:40:03 taft-01 qarshd[18513]: Talking to peer 10.15.80.47:44845 >May 13 12:40:03 taft-01 qarshd[18513]: Running cmdline: lvs -o copy_percent --noheadings helter_skelter/syncd_log_2legs_3 >May 13 12:40:03 taft-01 xinetd[6223]: EXIT: qarsh status=0 pid=18513 duration=0(sec) >May 13 12:40:20 taft-01 xinetd[6223]: START: qarsh pid=18516 from=10.15.80.47 >May 13 12:40:20 taft-01 qarshd[18516]: Talking to peer 10.15.80.47:44855 >May 13 12:40:20 taft-01 qarshd[18516]: Running cmdline: /usr/tests/sts-rhel5.2/bin/checkit -w /mnt/syncd_log_2legs_1/checkit -f /tmp/checkit_syncd_log_2legs_1 -v >May 13 12:40:22 taft-01 xinetd[6223]: EXIT: qarsh status=0 pid=18516 duration=2(sec) >May 13 12:40:29 taft-01 clogd[6683]: Invalid request_type >May 13 12:40:44 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/2031057] - retrying >May 13 12:40:45 taft-01 clogd[6683]: Invalid request_type >May 13 12:41:00 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/2031345] - retrying >May 13 12:41:15 taft-01 clogd[6683]: Invalid request_type >May 13 12:41:30 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/2032404] - retrying >May 13 12:41:45 taft-01 clogd[6683]: Invalid request_type >May 13 12:41:45 taft-01 clogd[6683]: Invalid request_type >May 13 12:42:00 taft-01 kernel: device-mapper: dm-log-clustered: [bVfiTlmM] Request timed out: [DM_CLOG_GET_RESYNC_WORK/2032871] - retrying >May 13 12:42:00 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/2033352] - retrying >May 13 12:45:48 taft-01 clogd[6683]: Invalid request_type >May 13 12:46:03 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_MARK_REGION/2042139] - retrying >May 13 12:46:03 taft-01 clogd[6683]: Invalid request_type >May 13 12:46:18 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/2042517] - retrying >May 13 12:50:27 taft-01 clogd[6683]: Invalid request_type >May 13 12:50:42 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/2052073] - retrying >May 13 12:51:32 taft-01 clogd[6683]: Invalid request_type >May 13 12:51:47 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/0] - retrying >May 13 12:56:21 taft-01 clogd[6683]: Invalid request_type >May 13 12:56:36 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_MARK_REGION/2065193] - retrying >May 13 12:59:03 taft-01 clogd[6683]: Invalid request_type >May 13 12:59:18 taft-01 kernel: device-mapper: dm-log-clustered: [bVfiTlmM] Request timed out: [DM_CLOG_IN_SYNC/0] - retrying >May 13 13:01:25 taft-01 clogd[6683]: Invalid request_type >May 13 13:01:40 taft-01 kernel: device-mapper: dm-log-clustered: [bVfiTlmM] Request timed out: [DM_CLOG_IN_SYNC/2077358] - retrying >May 13 13:10:21 taft-01 clogd[6683]: Invalid request_type >May 13 13:10:36 taft-01 kernel: device-mapper: dm-log-clustered: [bVfiTlmM] Request timed out: [DM_CLOG_IN_SYNC/0] - retrying >May 13 13:10:47 taft-01 clogd[6683]: Invalid request_type >May 13 13:11:02 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/2099907] - retrying >May 13 13:11:07 taft-01 clogd[6683]: Invalid request_type >May 13 13:11:22 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/2101317] - retrying >May 13 13:11:57 taft-01 clogd[6683]: Invalid request_type >May 13 13:12:12 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/2103182] - retrying >May 13 13:13:33 taft-01 clogd[6683]: Invalid request_type >May 13 13:13:48 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/2106509] - retrying >May 13 13:15:50 taft-01 clogd[6683]: Invalid request_type >May 13 13:16:05 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/2111285] - retrying >May 13 13:16:20 taft-01 clogd[6683]: Invalid request_type >May 13 13:16:35 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/2111865] - retrying >May 13 13:19:28 taft-01 clogd[6683]: Invalid request_type >May 13 13:19:43 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/0] - retrying >May 13 13:30:36 taft-01 clogd[6683]: Invalid request_type >May 13 13:30:51 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/2143705] - retrying >May 13 13:34:29 taft-01 clogd[6683]: Invalid request_type >May 13 13:34:44 taft-01 kernel: device-mapper: dm-log-clustered: [bVfiTlmM] Request timed out: [DM_CLOG_IN_SYNC/2152605] - retrying >May 13 13:39:28 taft-01 clogd[6683]: Invalid request_type >May 13 13:39:43 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/2163947] - retrying >May 13 13:40:28 taft-01 clogd[6683]: Invalid request_type >May 13 13:40:43 taft-01 kernel: device-mapper: dm-log-clustered: [bVfiTlmM] Request timed out: [DM_CLOG_GET_RESYNC_WORK/2166372] - retrying >May 13 13:40:44 taft-01 clogd[6683]: Invalid request_type >May 13 13:40:59 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/2167252] - retrying >May 13 13:44:33 taft-01 dhclient: DHCPREQUEST on eth0 to 10.15.89.100 port 67 >May 13 13:44:33 taft-01 dhclient: DHCPACK from 10.15.89.100 >May 13 13:44:33 taft-01 dhclient: bound to 10.15.89.67 -- renewal in 9301 seconds. >May 13 13:46:03 taft-01 clogd[6683]: Invalid request_type >May 13 13:46:18 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/2178424] - retrying >May 13 13:48:09 taft-01 clogd[6683]: Invalid request_type >May 13 13:48:24 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/2182931] - retrying >May 13 13:49:10 taft-01 clogd[6683]: Invalid request_type >May 13 13:49:25 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/2185173] - retrying >May 13 13:52:48 taft-01 clogd[6683]: Invalid request_type >May 13 13:53:03 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_GET_RESYNC_WORK/0] - retrying >May 13 13:59:23 taft-01 clogd[6683]: Invalid request_type >May 13 13:59:38 taft-01 kernel: device-mapper: dm-log-clustered: [bVfiTlmM] Request timed out: [DM_CLOG_IN_SYNC/2207348] - retrying >May 13 14:00:23 taft-01 clogd[6683]: Invalid request_type >May 13 14:00:38 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/2208963] - retrying >May 13 14:00:48 taft-01 clogd[6683]: Invalid request_type >May 13 14:01:03 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/2209933] - retrying >May 13 14:01:04 taft-01 clogd[6683]: Invalid request_type >May 13 14:01:19 taft-01 kernel: device-mapper: dm-log-clustered: [bVfiTlmM] Request timed out: [DM_CLOG_CLEAR_REGION/2210510] - retrying >May 13 14:18:37 taft-01 clogd[6683]: Invalid request_type >May 13 14:18:37 taft-01 clogd[6683]: Invalid request_type >May 13 14:18:52 taft-01 kernel: device-mapper: dm-log-clustered: [bVfiTlmM] Request timed out: [DM_CLOG_IN_SYNC/2251554] - retrying >May 13 14:18:52 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/2251577] - retrying >May 13 14:19:07 taft-01 clogd[6683]: Invalid request_type >May 13 14:19:22 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/2252462] - retrying >May 13 14:20:18 taft-01 clogd[6683]: Invalid request_type >May 13 14:20:33 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/2255487] - retrying >May 13 14:22:24 taft-01 clogd[6683]: Invalid request_type >May 13 14:22:40 taft-01 kernel: device-mapper: dm-log-clustered: [bVfiTlmM] Request timed out: [DM_CLOG_GET_RESYNC_WORK/2259731] - retrying >May 13 14:22:55 taft-01 clogd[6683]: Invalid request_type >May 13 14:23:10 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/2260730] - retrying >May 13 14:25:47 taft-01 clogd[6683]: Invalid request_type >May 13 14:26:02 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_GET_RESYNC_WORK/2267008] - retrying >May 13 14:26:02 taft-01 clogd[6683]: Invalid request_type >May 13 14:26:17 taft-01 kernel: device-mapper: dm-log-clustered: [bVfiTlmM] Request timed out: [DM_CLOG_CLEAR_REGION/2267168] - retrying >May 13 14:26:17 taft-01 clogd[6683]: Invalid request_type >May 13 14:26:32 taft-01 kernel: device-mapper: dm-log-clustered: [bVfiTlmM] Request timed out: [DM_CLOG_IN_SYNC/0] - retrying >May 13 14:27:38 taft-01 clogd[6683]: Invalid request_type >May 13 14:27:53 taft-01 kernel: device-mapper: dm-log-clustered: [ze7nw6EY] Request timed out: [DM_CLOG_IN_SYNC/0] - retrying >May 13 14:31:36 taft-01 clogd[6683]: Invalid request_type >May 13 14:31:51 taft-01 kernel: device-mapper: dm-log-clustered: [3RAr2F8m] Request timed out: [DM_CLOG_IN_SYNC/2279185] - retrying
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 446255
: 305290 |
305291
|
305292
|
305293