From owner-freebsd-current@FreeBSD.ORG Thu Dec 4 22:14:59 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 0A382106564A for ; Thu, 4 Dec 2008 22:14:59 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 694638FC12 for ; Thu, 4 Dec 2008 22:14:58 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (unknown [74.193.182.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 22FFF84CA43B; Thu, 4 Dec 2008 16:14:57 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id mB4MEpbA031182; Thu, 4 Dec 2008 16:14:52 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Thu, 4 Dec 2008 16:14:51 -0600 (CST) From: Wes Morgan To: Thomas Vogt In-Reply-To: Message-ID: References: <20081117205526.GC1733@garage.freebsd.pl> <20081202203308.GA13818@hyperion.scode.org> <200812021254.21242.fjwcash@gmail.com> <20081202232924.GA19134@hyperion.scode.org> <31C70CBC-488A-4A9A-A642-37855E8F1DD1@lassitu.de> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Current , Stefan Bethke Subject: Re: HEADS UP: New ZFS in the tree. 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: Thu, 04 Dec 2008 22:14:59 -0000 On Thu, 4 Dec 2008, Thomas Vogt wrote: > Hello Stefan > > Am 04.12.2008 um 00:33 schrieb Stefan Bethke: >> Am 03.12.2008 um 00:29 schrieb Peter Schuller: >> >>>> I've noticed the past couple of days, when using the server (not very >>>> often), every now and then, the GUI (KDE 4.1) will "hang" for up to 5 >>>> minutes (no mouse movement, no keyboard events), while the drives work >>>> like >>>> crazy. >>> >>> I was not explicit about it, but FWIW in my case the hang is not due >>> to drive saturation. The drives were mostly idle (except some stuff >>> triggered by a buildworld I had going) during the extended period of >>> ktorrent being unkillable. But again I never had this happen >>> pre-CURRENT. >> >> Just a very brief "me too" (but possibly different effect): I'm stress >> testing two machines I put together over the weekend with an endless loop >> of make -j4 universe, with /usr/obj on ZFS, with a single disk. One of the >> two machines has now been stuck for a couple of hours, and trying to access >> /tank results in a hung process, as will zfs list. >> >> I'll reboot and see what happens, and if I can trigger it again, willt try >> to produce more details. >> >> I have set >> vfs.zfs.arc_max="512M" >> vfs.zfs.prefetch_disable=1 >> in loader.conf >> >> FreeBSD lokschuppen.lassitu.de 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Wed Dec >> 3 07:05:03 UTC 2008 >> root@lokschuppen.lassitu.de:/usr/obj/usr/src/sys/EISENBOOT amd64 > > Try to disable ZIL in loader.conf: > vfs.zfs.zil_disable="1" > > It helped me to stop deadlocks during rsync processes. As long as you don't > run any databases or any fsync() intensiv applications, i don't see any > drawbacks in disabling zil. The drawbacks are for the applications itself not > for ZFS. ZFS will be always consistent on disk due to its transaction model > even without ZIL. Are you sure about that? Without the ZIL, wouldn't you need to scrub each pool after every crash, much as fsck with UFS?