From owner-freebsd-fs@FreeBSD.ORG Mon Jun 11 13:52:10 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C43661065673; Mon, 11 Jun 2012 13:52:10 +0000 (UTC) (envelope-from patpro@patpro.net) Received: from rack.patpro.net (rack.patpro.net [193.30.227.216]) by mx1.freebsd.org (Postfix) with ESMTP id 81BA08FC19; Mon, 11 Jun 2012 13:52:10 +0000 (UTC) Received: from rack.patpro.net (localhost [127.0.0.1]) by rack.patpro.net (Postfix) with ESMTP id B21301CC020; Mon, 11 Jun 2012 15:52:09 +0200 (CEST) X-Virus-Scanned: amavisd-new at patpro.net Received: from amavis-at-patpro.net ([127.0.0.1]) by rack.patpro.net (rack.patpro.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uaw3_9RC2Qwt; Mon, 11 Jun 2012 15:52:04 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by rack.patpro.net (Postfix) with ESMTP; Mon, 11 Jun 2012 15:52:04 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Patrick Proniewski In-Reply-To: <4FD5743D.4030002@FreeBSD.org> Date: Mon, 11 Jun 2012 15:52:03 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <672674FB-5E5F-4C4B-834A-07CD77A07478@patpro.net> References: <9A54A14B-7DA4-48AD-8198-63A8572D3DB3@patpro.net> <4FD5743D.4030002@FreeBSD.org> To: Matthew Seaman X-Mailer: Apple Mail (2.1084) Cc: freebsd-fs@FreeBSD.org Subject: Re: [zfs] need help with a bug (PR 156781) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 13:52:10 -0000 On 11 juin 2012, at 06:29, Matthew Seaman wrote: > On 11/06/2012 00:36, Mark Felder wrote: >> FreeBSD 8.1 and 8.2 are actually quite old these days. I don't think >> this bug is reproducible on 8.3 or 9.0. Can you upgrade and report = back? >=20 > I'm seeing exactly this on stable/9. Seems to be triggered by doing > certain IO patterns -- so csup of the ports cvs repo and subsequent > checkout will cause the effect, but direct csup of the ports tree = doesn't. Ok, I'm not exactly relieved the bug hits also 9.0, but it's good news I = won't have to plan a remote upgrade of FreeBSD and ZFS over ssh. I = master the process, having done FreeBSD upgrades over ssh since 5.x = (either sources and binary way), but the less I do it, the better I = feel. > This is using a zpool created under 8.0-RELEASE and subsequently > updated. mine have been created under 8.1 and 8.2 respectively, as far as I = remember (btw, is there any way to list the change history of a system, = other than keeping manual trace of every updates/upgrades?). regards, patpro