From owner-freebsd-fs@FreeBSD.ORG Tue May 19 10:18:26 2015 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4BDC61D5 for ; Tue, 19 May 2015 10:18:26 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D4A241310 for ; Tue, 19 May 2015 10:18:25 +0000 (UTC) Received: by wicmx19 with SMTP id mx19so111088675wic.0 for ; Tue, 19 May 2015 03:18:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=nbLCOn2lsfNTQI2kkjW43J7zUcSQmdFa9U+Q0AQ6EQc=; b=SflQwhhzDqINqs+guEWiPijRPDwK27nFw/fwUZpgAXsyagLgkTc5fjAgh9cPYDHfwy z+F3KaTH083vwJjo7VXzBqU4FobVM8TCqUjRlfvcoYVDoFIV4x7FrF5FQlP0ZMPaqd3i TxxM9cb+c5C437egC33YnWT5qOGYoEAG6BnvVtEQOmhoByyLLGt0Sw5Pxa+RKvaIxTt3 JLZ1syK49u1cYbFpDkw2QfVMDOE3gKSAiKBfBsOkkuok5mAWQln4PASeBWhVrvEUb+Li p1xWPzEmGkyNy49GslMid+fXh57B++dcU2fP0XnK5XVbOFQ5FPx7iSIs691vw/Mtv6js Zfyg== X-Received: by 10.180.99.166 with SMTP id er6mr30428113wib.58.1432030704331; Tue, 19 May 2015 03:18:24 -0700 (PDT) Received: from brick.home (acyt45.neoplus.adsl.tpnet.pl. [83.11.203.45]) by mx.google.com with ESMTPSA id d14sm21069030wjn.30.2015.05.19.03.18.23 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 May 2015 03:18:23 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Tue, 19 May 2015 12:18:21 +0200 From: Edward Tomasz Napierala To: Willem Jan Withagen Cc: fs@freebsd.org Subject: Re: Unexpected reboot after ctld run into trouble. Message-ID: <20150519101821.GC3292@brick.home> References: <55573756.9070503@digiware.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55573756.9070503@digiware.nl> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2015 10:18:26 -0000 On 0516T1425, Willem Jan Withagen wrote: > Hi, > > Found the following in my logs: > Losts of > ---- > (0:4:0/0): Task Action: LUN Reset > (0:4:0/0): CTL Status: Command Completed Successfully > sonewconn: pcb 0xfffff8004e69e930: Listen queue overflow: 8 already in > queue awaiting acceptance (740688 occurrences) > (0:4:0/0): Task Action: LUN Reset > (0:4:0/0): CTL Status: Command Completed Successfully > sonewconn: pcb 0xfffff8004e69e930: Listen queue overflow: 8 already in > queue awaiting acceptance (713721 occurrences) > (0:4:0/0): Task Action: LUN Reset > (0:4:0/0): CTL Status: Command Completed Successfully > sonewconn: pcb 0xfffff8004e69e930: Listen queue overflow: 8 already in > queue awaiting acceptance (691776 occurrences) > ---- > > Which then ends in: > ---- > panic: deadlkres: possible deadlock detected for 0xfffff8001ee94920, > blocked for 1801009 ticks > > > cpuid = 1 > Uptime: 14d13h13m47s > Dumping 7557 out of 8175 > MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%Table 'FACP' at > 0xcfedbcf8 > ---- > > The system is running ZFS with ZFS-on-root: > FreeBSD zfs.digiware.nl 10.1-STABLE FreeBSD 10.1-STABLE #221 r282282: > Fri May 1 06:51:41 CEST 2015 > > This could stem from the fact that I woke up my Win8 PC which has a > iscsi volume mounted. It is used to store security cam captures on and > does have somewhat bigger traffic on it. > > Suggestions or question to look at are welcom. > > --WjW > > > I do have a core in /var/crash, but will need some guidance to retreive > stuff from it. Could you send me the /var/crash/core.txt.N for that crashdump?