From owner-freebsd-current@FreeBSD.ORG  Mon Jul  7 18:45:54 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 70FFC1065678;
	Mon,  7 Jul 2008 18:45:54 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 84DB88FC18;
	Mon,  7 Jul 2008 18:45:53 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <48726462.3090009@FreeBSD.org>
Date: Mon, 07 Jul 2008 20:45:54 +0200
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: gnn@FreeBSD.org
References: <m2r6a9poww.wl%gnn@neville-neil.com>	<g4tgaf$vbt$1@ger.gmane.org>	<m2d4lpr2cj.wl%gnn@neville-neil.com>	<48726140.2000405@FreeBSD.org>
	<m2abgtr115.wl%gnn@neville-neil.com>
In-Reply-To: <m2abgtr115.wl%gnn@neville-neil.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@FreeBSD.org, Mark Atkinson <atkin901@yahoo.com>
Subject: Re: Has anyone else seen any form of in memory or
	on	disk	corruption?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jul 2008 18:45:54 -0000

gnn@FreeBSD.org wrote:
> At Mon, 07 Jul 2008 20:32:32 +0200,
> Kris Kennaway wrote:
>> gnn@freebsd.org wrote:
>>> At Mon, 07 Jul 2008 09:30:07 -0700,
>>> Mark Atkinson wrote:
>>>> Have you tried turning off background fsck on boot to see if the problem
>>>> goes away?
>>> The problem persists even without background fsck.
>>>
>>> I am starting to lean towards some sort of weird gzip bug, but have no
>>> real evidence yet.
>> Did you try zfs yet?  It will differentiate between corruption that 
>> occurs above (or in) or below the filesystem layer.
>>
> 
> Not as yet, that is on the list though.
> 
> Later,
> George
> 
> 

OK, might be worth the time investment IMO, unless you have other ideas 
to run down.

Kris