From owner-freebsd-questions@FreeBSD.ORG  Sat Sep  1 16:11:30 2007
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D000416A419
	for <freebsd-questions@freebsd.org>;
	Sat,  1 Sep 2007 16:11:30 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36])
	by mx1.freebsd.org (Postfix) with ESMTP id 2ED1613C467;
	Sat,  1 Sep 2007 16:11:30 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <46D98F2F.9060608@FreeBSD.org>
Date: Sat, 01 Sep 2007 18:11:27 +0200
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Per olof Ljungmark <peo@intersonic.se>
References: <46D90C6B.8070807@intersonic.se> <46D947BC.8000201@FreeBSD.org>
	<46D986F8.8090707@intersonic.se>
In-Reply-To: <46D986F8.8090707@intersonic.se>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-questions@freebsd.org
Subject: Re: g_vfs write error = 28, bad memory?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Sep 2007 16:11:30 -0000

Per olof Ljungmark wrote:
> 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.

It's not, unless something is explicitly creating it each time you boot. 
  Perhaps you are using a rc.conf setting that creates a md /tmp.

Kris