From owner-freebsd-stable@FreeBSD.ORG Tue Oct 14 01:15:59 2014 Return-Path: Delivered-To: freebsd-stable@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 9C5426B0; Tue, 14 Oct 2014 01:15:59 +0000 (UTC) Received: from mail-yk0-x235.google.com (mail-yk0-x235.google.com [IPv6:2607:f8b0:4002:c07::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A26BD6C; Tue, 14 Oct 2014 01:15:59 +0000 (UTC) Received: by mail-yk0-f181.google.com with SMTP id q200so3925603ykb.40 for ; Mon, 13 Oct 2014 18:15:58 -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:message-id:subject :from:to:cc:content-type; bh=oqg72uyd7A6ysA/Jre/9gGgkOX8P5fjPtNjpQ0dRirI=; b=nccjuB8TWlrxdg7X2JIQ3UMQ0IQ1yaD2gZpw0YO/VNcaBV2paBJ5qUYR0FCatyk3z9 J6wrMVKPcG//A8JNXZRlIhwLMv2aXx/7oHVPypXgyBMiPqmaXE8totx0Ya7XKyseFaTp 1LF7GELvD/H3rhge39KBRgvw1iHDa3/D9r/amC/DoBgx104NhjCqcPEMRqnbUap3JMyc 8Mq66qjBZORZNbFqumLtr9BAzy7M+kBb6/j8Sdqr4BytlHd6Zp4z3Z7ekX0JadvNBm3d EgqXN7K8ngy12zgyJ+4BVFFsvPXmJp/Y9nmvvwLBIOxtFz3yw5DgOdjM4t7Cp97Z2LYn EyDQ== MIME-Version: 1.0 X-Received: by 10.236.199.46 with SMTP id w34mr3092953yhn.20.1413249358423; Mon, 13 Oct 2014 18:15:58 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.170.82.197 with HTTP; Mon, 13 Oct 2014 18:15:58 -0700 (PDT) In-Reply-To: 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> <543C3C47.4010208@ijs.si> Date: Mon, 13 Oct 2014 18:15:58 -0700 X-Google-Sender-Auth: MmfIWfMdJ_ON90WeEuTiHDaEu-g Message-ID: Subject: Re: zpool import hangs when out of space - Was: zfs pool import hangs on [tx->tx_sync_done_cv] From: "K. Macy" To: Steven Hartland Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-fs@FreeBSD.org" , FreeBSD Stable , mark X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2014 01:15:59 -0000 >> 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... > > > Yer zfs list only shows around 2-3GB used too but zpool list > shows the pool is out of space. Cant rule out an accounting > issue though. > What is using the extra space in the pool? Is there an unmounted dataset or snapshot? Do you know how to easily tell? Unlike txg and zio processing I don't have the luxury of having just read that part of the codebase. Thanks.