From owner-freebsd-fs@freebsd.org  Fri Nov 20 13:17:36 2015
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49E77A3304A
 for <freebsd-fs@mailman.ysv.freebsd.org>; Fri, 20 Nov 2015 13:17:36 +0000 (UTC)
 (envelope-from rs@bytecamp.net)
Received: from mxout01.bytecamp.net (mxout01.bytecamp.net [212.204.60.217])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0AC4A129D
 for <freebsd-fs@freebsd.org>; Fri, 20 Nov 2015 13:17:35 +0000 (UTC)
 (envelope-from rs@bytecamp.net)
Received: by mxout01.bytecamp.net (Postfix, from userid 1001)
 id 2A9AB31519E; Fri, 20 Nov 2015 14:17:27 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bytecamp.net;
 h=subject:to:references:cc:from:message-id:date:mime-version:in-reply-to:content-type:content-transfer-encoding;
 s=20140709; bh=j3wHvGCkTy1dc3idv/yzCZpORWs=;
 b=FYxbNAW8SPEzR1k4v/QyW7OVZKfQneA/PaomcGHn4Psh5HVaWqfwOpN6w+PWswFu+Aeo98VYhHzdj+cnuV+fGJq27ke6AtppVXO+U8UgV+dgWItKZ929w5W5saTgC4wKW5hoWU09VdNHKrcJaMye58Ti9Kk0AqALSSpRmXBoTmA=
Received: from mail.bytecamp.net (mailstore.bytecamp.net [212.204.60.20])
 by mxout01.bytecamp.net (Postfix) with ESMTP id D5EEE3151A9
 for <freebsd-fs@freebsd.org>; Fri, 20 Nov 2015 14:17:26 +0100 (CET)
Received: (qmail 50513 invoked by uid 89); 20 Nov 2015 14:17:26 +0100
Received: from stella.bytecamp.net (HELO ?212.204.60.37?)
 (rs%bytecamp.net@212.204.60.37)
 by mail.bytecamp.net with AES128-SHA encrypted SMTP; 20 Nov 2015 14:17:26 +0100
Subject: Re: filesystem deadlock, process in vodead state
To: Yamagi Burmeister <lists@yamagi.org>
References: <564D9930.1080509@bytecamp.net>
 <20151119173821.b3da4b7d92571b723d4c5e5f@yamagi.org>
Cc: freebsd-fs@freebsd.org
From: Robert Schulze <rs@bytecamp.net>
Organization: bytecamp GmbH
Message-ID: <564F1D66.2060806@bytecamp.net>
Date: Fri, 20 Nov 2015 14:17:26 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151119173821.b3da4b7d92571b723d4c5e5f@yamagi.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Nov 2015 13:17:36 -0000

Hi,

Am 19.11.2015 um 17:38 schrieb Yamagi Burmeister:
> Hello,
> last week I've observed a similar deadlock on a FreeBSD 10.2 machine
> with UFS filesystem. I haven't saved the procstat output because I
> suspected broken hardware (The SSD wearout indicator was down to 22.
> There weren't any ATA errors in dmesg)

the SSDs are completely new, SMART wear level indicator is at 100%.
By the way, I'm able to list directory entries from the affected tree
via zdb.

with kind regards,
Robert Schulze