From owner-freebsd-stable@FreeBSD.ORG Tue Oct 14 01:32:29 2014 Return-Path: Delivered-To: freebsd-stable@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 15AA3AD8; Tue, 14 Oct 2014 01:32:29 +0000 (UTC) Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) (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 B6BDFF1D; Tue, 14 Oct 2014 01:32:28 +0000 (UTC) Received: by mail-yk0-f180.google.com with SMTP id 142so3981126ykq.11 for ; Mon, 13 Oct 2014 18:32:27 -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=MM2GVLyT6Pehvu1oKKeJ4UpP2MiIgQ6VqLc9yOfdDts=; b=z1bNNuOfrK0vIXEmo/JeWKq/CxTQAv/lk+NIVz41KHBOdBn9ylniupC+lvBNhd/JxD fXe/XZQEfqHUtG3BT3RsDDtROc1AZ3R36qfRBrAskb2x/Qb3d2ZGdLvPxUqrwrOZCzx4 gIElWQxuHvH/zD1zFgYSGmKXW0MCEWDH5afeAr0l0UB84lFW+3Kda2HW534klvJ5Yb2k S63BeW+MkkWEDgIKV+inkJcus+L6XyeXcjxZW+WR/eOrOGO9feCNgn+Ud8RviNl5/b3M zDUmoaJ70WFYnkc33IShp5xaBu+hTnxbiY5dzY84zdEK0CbUFXFPbf2jisPLSJk7z63M rc2A== MIME-Version: 1.0 X-Received: by 10.236.231.161 with SMTP id l31mr2441674yhq.104.1413250347868; Mon, 13 Oct 2014 18:32:27 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.170.82.197 with HTTP; Mon, 13 Oct 2014 18:32:27 -0700 (PDT) In-Reply-To: <543C7B43.5020301@ijs.si> 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> <543C7B43.5020301@ijs.si> Date: Mon, 13 Oct 2014 18:32:27 -0700 X-Google-Sender-Auth: VfHbR0ZPCoKAbKWaADfhCwJ9OWQ 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: Mark Martinec Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-fs@FreeBSD.org" , FreeBSD Stable 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:32:29 -0000 On Mon, Oct 13, 2014 at 6:24 PM, Mark Martinec wrote: > On 10/14/2014 03:15, K. Macy wrote: >> >> 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. > > > Most likely the snapshots (regular periodic snapshots). > Changes after upgrading an OS can maybe take an additional 50% > of space (just guessing). Btw, ashift=12. > Still can't see how that would amount to 4 GiB, but it's possible. > Disconcerting. Is this something that others are likely to hit? Should accounting for writes fail with ENOSPC a bit earlier so that we never reach a state like this? I.e. non-metadata writes will fail at a lower threshold than data or if that is already the case, reduce the threshold further. -K