From owner-freebsd-fs@FreeBSD.ORG Sat May 10 05:18:00 2008 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 4B72D106566B for ; Sat, 10 May 2008 05:18:00 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (neo.vx.sk [213.239.219.9]) by mx1.freebsd.org (Postfix) with ESMTP id 0B4D38FC0C for ; Sat, 10 May 2008 05:17:59 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by mail.vx.sk (Postfix) with ESMTP id 386C1116CC for ; Sat, 10 May 2008 07:02:55 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk ([127.0.0.1]) by localhost (mail.vx.sk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id osDkn4Tqt6st for ; Sat, 10 May 2008 07:02:53 +0200 (CEST) Received: from [10.2.0.1] (f2-fiber.radiolan.sk [193.93.72.46]) by mail.vx.sk (Postfix) with ESMTPSA id 0ADC511472 for ; Sat, 10 May 2008 07:02:52 +0200 (CEST) Message-ID: <48252C89.8@FreeBSD.org> Date: Sat, 10 May 2008 07:03:05 +0200 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sk; rv:1.8.1.14) Gecko/20080421 Thunderbird/2.0.0.14 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: ZFS lockup in "zfs" state 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: Sat, 10 May 2008 05:18:00 -0000 Hi, I just experienced the same lockup in zfs state as other people did (Ivan Voras, Peter Schuller) - UFS filesystems still intact. There was heavy backup tar/gzip activity on the filesystem (read-only, write was to NFS) and lots of reads via NFS, the server was doing this job without problems for 11 days. FreeBSD: 7-STABLE 2008-04-29 ARCH: amd64 RAM: 6 GB ZFS: prefetch disabled vm.kmem_size_max="1073741824"