On Sep 14, 2005, at 4:13 PM, John-Mark Gurney wrote:
IIRC GEOM should handle ENOMEMs by retrying the IO, but I'm
asking just in
case - are these errors something I should worry about?
I/O errors suggest your disk is failing.
Unless for some reason his disk is running out of memory:
grep 12 /usr/include/errno.h
#define ENOMEM 12 /* Cannot allocate memory */
The error occurs when sys/vm/swap_pager:swapgeom_strategy() can't
allocate a copy of an underlying I/O request buffer. The log message
lies a bit; this isn't a physical disk I/O error.
--lyndon
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"