From owner-freebsd-ports@FreeBSD.ORG  Tue Nov 18 19:28:26 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@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 4206ECF5
 for <ports@freebsd.org>; Tue, 18 Nov 2014 19:28:26 +0000 (UTC)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (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 F05DF84B
 for <ports@freebsd.org>; Tue, 18 Nov 2014 19:28:25 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD))
 (envelope-from <lists@opsec.eu>) id 1XqoRs-000LXw-GK
 for ports@freebsd.org; Tue, 18 Nov 2014 20:28:24 +0100
Date: Tue, 18 Nov 2014 20:28:24 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: ports@freebsd.org
Subject: pkg hangs on 10.1 (ZFS-filesystem) in huge pkg update -f
Message-ID: <20141118192824.GO44537@home.opsec.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2014 19:28:26 -0000

Hi!

I have a test box (10.1-REL amd64, ZFS filesystem), where pkg hangs in a

pkg update -f

operation:

[448/2310] Reinstalling graphviz-2.38.0_2: 100%

load: 0.15  cmd: dot 13636 [urdlck] 42255.22r 0.01u 0.03s 0% 6548k
load: 0.15  cmd: dot 13636 [urdlck] 42255.39r 0.01u 0.03s 0% 6548k
load: 0.15  cmd: dot 13636 [urdlck] 42255.53r 0.01u 0.03s 0% 6548k
load: 0.15  cmd: dot 13636 [urdlck] 42255.69r 0.01u 0.03s 0% 6548k

I can still log on that box (ssh). Running a pkg info brings, after a while
(seen by the ctrl-t output):

load: 0.47  cmd: pkg 18350 [nanslp] 26.65r 0.00u 0.03s 0% 5808k
pkg: sqlite error while executing PRAGMA user_version; in file pkgdb.c:2291: database is locked

A ktrace on the urdlck'ed pid did not show anything:

ktrace -f /tmp/traceit -p 13636
[waiting a bit]
ktrace -C

and:

-rw-------  1 root  wheel  0 Nov 18 19:21 /tmp/traceit

I have no idea why updating graphviz causes dot to be run ?

Any ideas on how I can debug this further ?

-- 
pi@opsec.eu            +49 171 3101372                         6 years to go !