From owner-freebsd-fs@FreeBSD.ORG Thu Jan 16 06:47:02 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2DE21F3 for ; Thu, 16 Jan 2014 06:47:02 +0000 (UTC) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B3E531346 for ; Thu, 16 Jan 2014 06:47:01 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id z12so2689159wgg.18 for ; Wed, 15 Jan 2014 22:47:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:from:subject:date:to; bh=1VkXKFZpS0HUY9DPYdk5m/P0DwbMiXV0LshZT4pfIqU=; b=UmJzsN1pCe34BKycZ8hJTCU0Tq6+YnWWY5sMjaY9FhZq2OFj6MXFX7ha4BrZ9U69IW mCe5UXWt3100iXEzAJSWU/pNlg1ty++9PWNNEi5Uw1g2kEOpc/dfRD2YqRIV4VYYA0IL 7HDueWCaTBwJFP0A1BQBrH/QH6rDPzyew+eo075Li2AtaRCnN0Yqd5dNmZgSnLQQtndI CLC9aO52wmyyyVLQn3oCBByFrmoQoPAU284qaFOUMBkUzyUp3cDdKvjMvTLZoAjBCPnV MB0AYOAy9+2f0NHKro87U8RgpnByIb51H4d6qUrj0LDRY0I+Kcha7DaMrOVBi8IcsW6/ YAlg== X-Received: by 10.194.93.67 with SMTP id cs3mr6781157wjb.26.1389854817114; Wed, 15 Jan 2014 22:46:57 -0800 (PST) Received: from [192.168.0.10] (alf94-11-82-247-6-183.fbx.proxad.net. [82.247.6.183]) by mx.google.com with ESMTPSA id pl7sm5165229wjc.16.2014.01.15.22.46.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 Jan 2014 22:46:55 -0800 (PST) References: <20140115223403.GA69817@neutralgood.org> In-Reply-To: <20140115223403.GA69817@neutralgood.org> Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Message-Id: <628AA905-09F4-43DA-8EB0-820557EEFC79@gmail.com> X-Mailer: iPhone Mail (9A405) From: Gomes do Vale Victor Subject: Re: zpool import taking weeks ... Date: Thu, 16 Jan 2014 07:46:52 +0100 To: "kpneal@pobox.com" Cc: FreeBSD Filesystems X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jan 2014 06:47:02 -0000 Hi Le 15 janv. 2014 =C3=A0 23:34, kpneal@pobox.com a =C3=A9crit : > On Wed, Jan 15, 2014 at 09:29:27AM +0100, Ulysse 31 wrote: >> Thanks for the answer. >>=20 >> I was beginning to ... well ... have a little start of panic ^^' >> The import still running but no real activity on disks : sometimes, >> maybe something like each hour, there is some really brief led >> activity on the hdd, but nothing more. >> one thing that would be great is to have an overall percentage or just >> counting of what is done or what is left ... for now i don't even know >> if it's gonna end on the next 5 mins or on the next 5 weeks :s >> So now since i have no real activity on the actual zpool import (the >> last import started a week ago, it do not have go out of swap since i >> added lot of swap (260G HDD swap)), should i just let it run, or make >> a reboot and start over ? >=20 > Memory used by the ZFS DDT is (someone correct me if I'm wrong) kernel > memory that I don't think is swappable. So adding more swap space won't > help. (Again, correct me if I'm out of date or just wrong please.) >=20 Yes, it's kernel memory but appears as "wired" not as "used", and it does no= t change the fact that zpool import goes out of swap without the swap disk (= tested and approved). With the disk memory is all (64Gb) marked as wired (ke= rnel usage) plus 780Mo used in swap.=20 > Worse, keeping track of swap space takes kernel memory for the bookkeeping= . Again, I have tested zpool import WITHOUT the disk, and it as gone "out of s= wap" (out of memory) since I added the disk it as taken all mem plus swap. P= lease read my first and my post . > That memory for swap bookkeeping is memory that can't be used by ZFS. So > the large swap device you added is only making the situation worse. This > also implies that you'll get best results by not having any swap space > at all during the problematic import. You can re-add it once the import > is completed. >=20 I really don't know if ZFS can swap or not, what I know is that system and l= ivecd goes out of memory on import. One possible solution is simply ZFS takes all RAM leaving swap to user land .= .. But result is the same : machine crashes without it. > --=20 > Kevin P. Neal http://www.pobox.com/~kpn/ >=20 > Seen on bottom of IBM part number 1887724: > DO NOT EXPOSE MOUSE PAD TO DIRECT SUNLIGHT FOR EXTENDED PERIODS OF TIME.