From owner-freebsd-fs@FreeBSD.ORG  Sat Oct 20 14:45:57 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id C798E376;
 Sat, 20 Oct 2012 14:45:57 +0000 (UTC) (envelope-from dg17@penx.com)
Received: from btw.pki2.com (btw.pki2.com [IPv6:2001:470:a:6fd::2])
 by mx1.freebsd.org (Postfix) with ESMTP id 90B7A8FC16;
 Sat, 20 Oct 2012 14:45:57 +0000 (UTC)
Received: from [127.0.0.1] (localhost [127.0.0.1])
 by btw.pki2.com (8.14.5/8.14.5) with ESMTP id q9KEjoJE031200;
 Sat, 20 Oct 2012 07:45:50 -0700 (PDT) (envelope-from dg17@penx.com)
Subject: Re: ZFS hang status update
From: Dennis Glatting <dg17@penx.com>
To: Andriy Gapon <avg@freebsd.org>
In-Reply-To: <50825598.3070505@FreeBSD.org>
References: <1350698905.86715.33.camel@btw.pki2.com>
 <1350711509.86715.59.camel@btw.pki2.com>  <50825598.3070505@FreeBSD.org>
Content-Type: text/plain; charset="us-ascii"
Date: Sat, 20 Oct 2012 07:45:49 -0700
Message-ID: <1350744349.88577.10.camel@btw.pki2.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
X-yoursite-MailScanner-Information: Dennis Glatting
X-yoursite-MailScanner-ID: q9KEjoJE031200
X-yoursite-MailScanner: Found to be clean
X-MailScanner-From: dg17@penx.com
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: dg17@penx.com
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: Sat, 20 Oct 2012 14:45:57 -0000

On Sat, 2012-10-20 at 10:41 +0300, Andriy Gapon wrote:
> on 20/10/2012 08:38 Dennis Glatting said the following:
> > This is da0 (the cache --SSD) on which camcontrol hanged. It is on the
> > same controller.
> 
> Hmm, hanging camcontrol is a bad sign.  It would be interesting to get procstat
> -k information just for the hanging camcontrol process.
> Also, is it possible to eliminate this disk from the configuration?
> 

Eliminate disk: yes. However the device remains in the system (hope that
is ok -- will remove if you think best).

Config now:

mc# zpool status disk-1
  pool: disk-1
 state: ONLINE
  scan: scrub repaired 0 in 0h38m with 0 errors on Tue Oct 16 16:47:51
2012
config:

	NAME        STATE     READ WRITE CKSUM
	disk-1      ONLINE       0     0     0
	  raidz2-0  ONLINE       0     0     0
	    da5     ONLINE       0     0     0
	    da6     ONLINE       0     0     0
	    da7     ONLINE       0     0     0
	    da2     ONLINE       0     0     0
	    da3     ONLINE       0     0     0
	    da4     ONLINE       0     0     0

errors: No known data errors


I'll reboot and start the job anew.


If camcontrol hangs again, I'll procstat it.