From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 18:32:33 2008 Return-Path: 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 6E4561065687; Mon, 7 Jul 2008 18:32:33 +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 ABC408FC2D; Mon, 7 Jul 2008 18:32:31 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48726140.2000405@FreeBSD.org> Date: Mon, 07 Jul 2008 20:32:32 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: gnn@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Mark Atkinson 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 18:32:33 -0000 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. Kris