From owner-freebsd-stable@FreeBSD.ORG  Mon Feb 27 08:20:58 2012
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 61A77106564A
	for <freebsd-stable@freebsd.org>; Mon, 27 Feb 2012 08:20:58 +0000 (UTC)
	(envelope-from emz@norma.perm.ru)
Received: from elf.hq.norma.perm.ru (unknown [IPv6:2001:470:1f09:14c0::2])
	by mx1.freebsd.org (Postfix) with ESMTP id 108BB8FC0C
	for <freebsd-stable@freebsd.org>; Mon, 27 Feb 2012 08:20:57 +0000 (UTC)
Received: from bsdrookie.norma.com. ([IPv6:fd00::7fc])
	by elf.hq.norma.perm.ru (8.14.4/8.14.4) with ESMTP id q1R8KfBE027803
	(version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO)
	for <freebsd-stable@freebsd.org>; Mon, 27 Feb 2012 13:20:49 +0500 (YEKT)
	(envelope-from emz@norma.perm.ru)
Message-ID: <4F4B3CD9.9060704@norma.perm.ru>
Date: Mon, 27 Feb 2012 14:20:41 +0600
From: "Eugene M. Zheganin" <emz@norma.perm.ru>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:7.0) Gecko/20111001 Thunderbird/7.0
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
References: <4F4B0F83.4090600@norma.perm.ru>
	<4F4B3370.7020302@brockmann-consult.de>
In-Reply-To: <4F4B3370.7020302@brockmann-consult.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7
	(elf.hq.norma.perm.ru [IPv6:fd00::30a]);
	Mon, 27 Feb 2012 13:20:49 +0500 (YEKT)
X-Spam-Status: No hits=-98.5 bayes=0.5 testhits RDNS_NONE=0.793,
	SPF_SOFTFAIL=0.665,TO_NO_BRKTS_NORDNS=0.001,USER_IN_WHITELIST=-100
	autolearn=no version=3.3.2
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on elf.hq.norma.perm.ru
Subject: Re: zfs, 1 gig of RAM and periodic weekly
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2012 08:20:58 -0000

Hi.

On 27.02.2012 13:40, Peter Maloney wrote:
> 8.2-RELEASE is highly unstable with ZFS in my opinion. For example, my
> system with 48 GB of RAM would hang or crash for no apparent reason in
> random intervals. Upgrading in September fixed most of it, except 1
> random hang possibly related to NFS, and a hang when renaming snapshots
> with zvols [new problem after 8.2-RELEASE, PR 161968]. The renaming
> snapshot with zvols hang seems fixed since update again in February.
>
> Still unresolved though is that restarting nfsd makes nfsd hang until
> reboot. I don't know if 8.2-RELEASE had that problem.
>
> You should consider an update with csup. Make sure you test and monitor
> after the upgrade, in case some other funny issues come up, like my
> restarting nfsd issue. But of course I chose that over random hangs and
> panics.
>
> And one word of advice: If you want to upgrade your pools to v28, I
> think you should consider recreating your pools as v28 rather than
> upgrading. There are some side effects to upgrading, such as logs that
> can't be removed.
Well... I upgraded one machine and got kern/164400 immidiately. So it 
looks like I'm stuck.

Eugene.