Date: Tue, 10 Oct 2006 14:11:29 -0400 From: Mike Jakubik <mikej@rogers.com> To: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> Cc: Vivek Khera <vivek@khera.org>, stable@freebsd.org Subject: Re: gmirror warnings Message-ID: <452BE251.9090008@rogers.com> In-Reply-To: <20061010203856.K68266@atlantis.atlantis.dp.ua> References: <71E7CE6F-900A-419D-84C0-18B926377AED@khera.org> <20061010203856.K68266@atlantis.atlantis.dp.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
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 start >> >> Should I be worried about these warnings or are they just transient >> failures that correct themselves? > > 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, or at least more prone to occur. I have a number of identical servers, and only one of them runs in amd64 mode. This server displays these errors every now and then, while the others don't. While the server continues to function properly, its still annoying seeing these. Perhaps there is a auto tuning problem on amd64?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?452BE251.9090008>