From owner-freebsd-fs@FreeBSD.ORG  Thu Jan 31 08:44:37 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 37701254;
 Thu, 31 Jan 2013 08:44:37 +0000 (UTC) (envelope-from lev@FreeBSD.org)
Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru
 [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id DD28A2EE;
 Thu, 31 Jan 2013 08:44:36 +0000 (UTC)
Received: from lion.home.serebryakov.spb.ru (unknown
 [IPv6:2001:470:923f:1:2577:cf36:d0d4:4986])
 (Authenticated sender: lev@serebryakov.spb.ru)
 by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id B6CD34ACC7;
 Thu, 31 Jan 2013 12:44:28 +0400 (MSK)
Date: Thu, 31 Jan 2013 12:44:19 +0400
From: Lev Serebryakov <lev@FreeBSD.org>
Organization: FreeBSD
X-Priority: 3 (Normal)
Message-ID: <1291867.20130131124419@serebryakov.spb.ru>
To: freebsd-fs@FreeBSD.org, freebsd-stable@freebsd.org
Subject: 9.1-STABLE, live lock up,
 seems that it is ZFS lockup in "zfskern{txg_thread_enter}" state
 "tx->tx"
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: lev@FreeBSD.org
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jan 2013 08:44:37 -0000

Hello, freebsd-fs.

  I have 9.1-STABLE (r244958) system, amd64, 8GiB memory.

  Two SATA disks, 750Gb each.

  Disks are partitoned into 7 (BSD) partitons (exactly the same), 5 of
 these pairs are joined into gmirrors for "system" FSes (UFS2), one
 pair is used for swaps and 7th pair is used as zmirror for /usr/home.

   Tonight system becomes unusable, as every process which try to read
 directories in /usr/home (like "ls ~" or "find /usr/home -type f")
 hangs forever. I could login to system, login shell starts, but if I
 run "ls" right after -- it hangs. Every periodic process, which try
 to read home FS (directories, not files!) hangs. It looks, like
 stat() calls on this FS hangs, but not open()/read()/write()/close().

  One thing I fins suspicious in different system diagnostics, is
  kernel thread "zfskern{txg_thread_enter}" which is shown in state
  "tx->tx" forever.

  Disks looks completely OK according to smartd/smartctl, no hardware
 errors in dmesg, etc.

===============================================
# zpool status
  pool: pool
 state: ONLINE
status: The pool is formatted using a legacy on-disk format.  The pool can
        still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'.  Once this is done, the
        pool will no longer be accessible on software that does not support feature
        flags.
  scan: resilvered 32.1G in 0h34m with 0 errors on Sat Jun  2 16:22:59 2012
config:

        NAME         STATE     READ WRITE CKSUM
        pool         ONLINE       0     0     0
          mirror-0   ONLINE       0     0     0
            ada0s1h  ONLINE       0     0     0
            ada1s1h  ONLINE       0     0     0

errors: No known data errors
================================================


-- 
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>