Date: Sat, 01 Sep 2007 17:36:24 +0200 From: Per olof Ljungmark <peo@intersonic.se> To: Kris Kennaway <kris@FreeBSD.org> Cc: freebsd-questions@freebsd.org Subject: Re: g_vfs write error = 28, bad memory? Message-ID: <46D986F8.8090707@intersonic.se> In-Reply-To: <46D947BC.8000201@FreeBSD.org> References: <46D90C6B.8070807@intersonic.se> <46D947BC.8000201@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > Per olof Ljungmark wrote: >> I use a memory file system for some tmp files and last night I saw >> this, followed by a reboot. Bad memory? 6-STABLE from April.. >> >> foo-bar kernel: g_vfs_done():md0[WRITE(offset=259244032, >> length=131072)]error = 28 >> foo-bar kernel: g_vfs_done():md0[WRITE(offset=259375104, >> length=131072)]error = 28 >> [ten more lines...] >> [reboot] >> >> Thanks, > > #define ENOSPC 28 /* No space left on device */ > > You are probably (incorrectly) using a malloc backed disk. Use swap > backing and you won't panic when memory is low. Yes, sounds likely, thanks. One more question then, where is the md information stored through a reboot? I did not edit rc.conf or fstab or kernel config but still /dev/md0 came back up. Hmmm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46D986F8.8090707>