I'm now starting to get worried... last night the box spewed forth
these:
dtfe2 kernel log messages:
+++ /tmp/security.N8067F3a Wed Oct 11 03:03:32 2006
+g_post_event_x(0x80210a70, 0xff0016c551a0, 2, 262144)
+g_post_event_x(0x80210a70, 0xff003c90cc20, 2, 262144)
Vivek Khera wrote:
I'm now starting to get worried... last night the box spewed forth
these:
dtfe2 kernel log messages:
+++ /tmp/security.N8067F3a Wed Oct 11 03:03:32 2006
+g_post_event_x(0x80210a70, 0xff0016c551a0, 2, 262144)
+g_post_event_x(0x80210a70,
On Oct 11, 2006, at 10:57 AM, Oliver Fromme wrote:
Vivek Khera wrote:
I'm now starting to get worried... last night the box spewed forth
these:
dtfe2 kernel log messages:
+++ /tmp/security.N8067F3a Wed Oct 11 03:03:32 2006
+g_post_event_x(0x80210a70, 0xff0016c551a0, 2,
Hello!
On Tue, 10 Oct 2006, Vivek Khera wrote:
Over the weekend and today we got some curious error messages from gmirror
providers:
Oct 7 03:02:14 dtfe2 kernel: ad6: FAILURE - out of memory in start
Oct 7 04:15:58 dtfe2 kernel: ad4: FAILURE - out of memory in start
Should I be worried
Dmitry Pryanishnikov wrote:
Hello!
On Tue, 10 Oct 2006, Vivek Khera wrote:
Over the weekend and today we got some curious error messages from
gmirror providers:
Oct 7 03:02:14 dtfe2 kernel: ad6: FAILURE - out of memory in start
Oct 7 04:15:58 dtfe2 kernel: ad4: FAILURE - out of memory in
Vivek Khera wrote:
On Oct 10, 2006, at 2:11 PM, Mike Jakubik wrote:
Those messages are not directly related to gmirror, they come from
the ATA
driver when it can't allocate memory for the structure which describes
I/O request:
I think this behavior is limited to the amd64 architecture,