From owner-freebsd-fs@FreeBSD.ORG  Sat Oct 20 16:04:35 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 520876C4;
 Sat, 20 Oct 2012 16:04:35 +0000 (UTC)
 (envelope-from artemb@gmail.com)
Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com
 [209.85.217.182])
 by mx1.freebsd.org (Postfix) with ESMTP id 8D25F8FC0C;
 Sat, 20 Oct 2012 16:04:34 +0000 (UTC)
Received: by mail-lb0-f182.google.com with SMTP id b5so1167445lbd.13
 for <multiple recipients>; Sat, 20 Oct 2012 09:04:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date
 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
 bh=qLpQAEIqoDU3au/8LZjSGP4J3hjCg8WEp4OVma32acM=;
 b=tQF3OqZ0WSd0PqIk6J4ICf2LeKum8T5yBN+IwFOLyrum7B33h7LcWCCXj8wnSLN0IF
 ZgkEB5FbyY0hClVGJ7ScTnmF1R+Mm7jETmfoeLhgY5cBIdRDYO/DrzNFZ4xwGry09lde
 F3DfHFe7AC7dygZj0OUdE/YFCCcc/1tf/4Xv/PJ7CFlYmlcWwjN2MKlH7+Kt34v6r2k4
 MjY2i0blwAwz+FzW8qqHQ+/nOYhzMDixfAZ3RhOoBdFMchTHXALILgWUsifdCRjBzSWc
 8LslTuBWMTRlP68lHQtwkawVNgR6uuM9z7IylULu/10htgu3Xn+XOjPi6ADkGkd3J9/9
 hF5A==
MIME-Version: 1.0
Received: by 10.112.29.9 with SMTP id f9mr1840212lbh.22.1350749073251; Sat, 20
 Oct 2012 09:04:33 -0700 (PDT)
Sender: artemb@gmail.com
Received: by 10.112.27.161 with HTTP; Sat, 20 Oct 2012 09:04:33 -0700 (PDT)
In-Reply-To: <1350711509.86715.59.camel@btw.pki2.com>
References: <1350698905.86715.33.camel@btw.pki2.com>
 <1350711509.86715.59.camel@btw.pki2.com>
Date: Sat, 20 Oct 2012 09:04:33 -0700
X-Google-Sender-Auth: ASKwcj0ZuYF5k8Z43bcne2fE3us
Message-ID: <CAFqOu6gE2m9B2y_FkSD3zNxO8_770VmZRb2huio0ir4msf57Wg@mail.gmail.com>
Subject: Re: ZFS hang status update
From: Artem Belevich <art@freebsd.org>
To: Dennis Glatting <freebsd@pki2.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-fs@freebsd.org, Andriy Gapon <avg@freebsd.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
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 16:04:35 -0000

On Fri, Oct 19, 2012 at 10:38 PM, Dennis Glatting <freebsd@pki2.com> wrote:
> This is da0 (the cache --SSD) on which camcontrol hanged. It is on the
> same controller.
>
> da0 at mps0 bus 0 scbus0 target 3 lun 0
> da0: <ATA M4-CT256M4SSD2 000F> Fixed Direct Access SCSI-6 device
> da0: 600.000MB/s transfers
> da0: Command Queueing enabled
> da0: 244198MB (500118192 512 byte sectors: 255H 63S/T 31130C)

Hmm.. It may be a coincidence, but at work I do see same 256G M4 SSDs
used as L2ARC+swap hanging now and then. In my case they are connected
to SATA2 on Supermicro X8DTi-F motherboard (ICH10?) running
FreeBSD8-stable/amd64.

It does not happen often -- few times for the last half a year or so.
I was hoping that new firmware would fix the issue, but firmware rev
000f still hangs.

Crucial had released new firmware (010G) few weeks back but I didn't try it yet.

--Artem