From owner-freebsd-fs@FreeBSD.ORG Mon Oct 13 20:55:43 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 03DAB7A1; Mon, 13 Oct 2014 20:55:43 +0000 (UTC) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) by mx1.freebsd.org (Postfix) with ESMTP id 80D49DE6; Mon, 13 Oct 2014 20:55:42 +0000 (UTC) Received: from amavis-proxy-ori.ijs.si (localhost [IPv6:::1]) by mail.ijs.si (Postfix) with ESMTP id 3jGsbw4pMNzNr; Mon, 13 Oct 2014 22:55:40 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:subject:subject:mime-version:user-agent:from:from :date:date:message-id:received:received:received; s=jakla4; t= 1413233736; x=1415825737; bh=6vVXfSie0JrMZ/XRKkdzqrFhYP73Kvzoe9z 5MW9q7cg=; b=FcmCvr5bkoqpBHw1IS279ppSl6ayjJqUiaDl0rgvZ8J+QuEkfZ2 rU94jkMQko9tvYD853yVtoBLmt8CR2d6mk25JiOH/DHNLMvFvV4NlwDkzVKxse3H eG1/ck+EEqLs6cNuMSgTvzMP7QDcF2KKP+gkhh5AMUagPC0LEDxhp3bo= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-proxy-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10012) with ESMTP id nPgztBolmqQc; Mon, 13 Oct 2014 22:55:36 +0200 (CEST) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP; Mon, 13 Oct 2014 22:55:36 +0200 (CEST) Received: from sleepy.ijs.si (msleepy-1-pt.tunnel.tserv27.prg1.ipv6.he.net [IPv6:2001:470:6e:18e::2]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mildred.ijs.si (Postfix) with ESMTPSA id 3jGsbq6N3lzSJ; Mon, 13 Oct 2014 22:55:35 +0200 (CEST) Message-ID: <543C3C47.4010208@ijs.si> Date: Mon, 13 Oct 2014 22:55:35 +0200 From: mark User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: zpool import hangs when out of space - Was: zfs pool import hangs on [tx->tx_sync_done_cv] References: <54372173.1010100@ijs.si> <644FA8299BF848E599B82D2C2C298EA7@multiplay.co.uk> <54372EBA.1000908@ijs.si> <543731F3.8090701@ijs.si> <543AE740.7000808@ijs.si> <6E01BBEDA9984CCDA14F290D26A8E14D@multiplay.co.uk> <14ADE02801754E028D9A0EAB4A16527E@multiplay.co.uk> In-Reply-To: <14ADE02801754E028D9A0EAB4A16527E@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2014 20:55:43 -0000 On 10/13/2014 22:10, Steven Hartland wrote: > So the issue is simply the pool is out of space to perform the import > as that process, when not readonly, requires space to write to the pool. > > The problem with that is that during this process it has the pool lock so > any subsequent zpool actions are dead in the water as they will block > waiting on that lock. > > Something to discuss with the openzfs guys, but I would say the import > should fail with a no space error. > > So Mark the mystery is solved, when you upgraded you ran the pool so low > on space that it now can't be imported RW as that requires a write. > > Regards > Steve Thank you both for analysis and effort! I can't rule out the possibility that my main system pool on a SSD was low on space at some point in time, but the three 4 GiB cloned pools (sys1boot and its brothers) were all created as a zfs send / receive copies of the main / (root) file system and I haven't noticed anything unusual during syncing. This syncing was done manually (using zxfer) and independently from the upgrade on the system - on a steady/quiet system, when the source file system definitely had sufficient free space. The source file system now shows 1.2 GiB of usage shown by df: shiny/ROOT 61758388 1271620 60486768 2% / Seems unlikely that the 1.2 GiB has grown to 4 GiB space on a cloned filesystem. Will try to import the main two pools after re-creating a sane boot pool... Mark