From owner-freebsd-fs@freebsd.org Mon May 2 07:53:43 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1755CB2AF19 for ; Mon, 2 May 2016 07:53:43 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-yw0-x244.google.com (mail-yw0-x244.google.com [IPv6:2607:f8b0:4002:c05::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE8DF10E9 for ; Mon, 2 May 2016 07:53:42 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by mail-yw0-x244.google.com with SMTP id v81so18462455ywa.2 for ; Mon, 02 May 2016 00:53:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=1HDs2mS6VZkE0rSFrjn3UJNGFQfnf0NeOWqDEIh/j+Y=; b=ic8Z9lN5CdmwMMVwRQu/8F9V6O8B4D5bft2NDonqseqiS8JN7GT2aiMqVFhht4mAQk S+dcHUPXBnoA+c5mp7HE/vn7OeiZftzCi5KveZzf05oa2MKF/F4UxWQc9Nh6Gl46HV84 CXIzVtrzfZG4c99mqBYkz8YfXxztJ026RkWDLjKhVi61LLHSA5A+05yywm+sYkpNS/hw X2/DuAI2yITnbac+fttPq0W88dxEZ2Gp5E8TNRwcJqeofQtp9IXl7R8xESFp/UslA7Wx eZ3NOEfdhWBLGUN7WOPdqXgG5UIJ4KWWtUnMeOM5rCEzL//+8qWBdTqlA0W28i9xhFa7 +Q/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=1HDs2mS6VZkE0rSFrjn3UJNGFQfnf0NeOWqDEIh/j+Y=; b=B7DYJo4yo3M8eLFaUlDAqfu6WMgiBeD+uveUS1Jzn+dil3PES1iJPedc+OGA4wLhOY gdhymh18bB6gIYJs9Eoy24E84AIfca72cVAWZQf24QQWeRfBs2zBdhmhtjXbSe5sF4wL 4F5OByqrbPCHeWTN1vibCr4ylfBHRi9kRcWMfq/TFRfVBcgPMrq41SkdFlWH2Xoz6u4I hgTBJa4F+A5icg0RRu1rVUzRIKRSeImMKndBooWJBOWALoCUSnxZQD8/Ms/utInGTIgQ Oh5i3YcHFvVnxVrFihbxFhHafrGXYLj7zLbjMbh8idseva4FY9KtFk92s3b/2fHT7UMD D2pg== X-Gm-Message-State: AOPr4FVs3O+1sMrrsk7f5TWG4IHzcXCiUuJbxvypn5OvYuNQMiyyrqzd6siP5At3YhvM3zU58t6z+F35br183Q== MIME-Version: 1.0 X-Received: by 10.176.2.52 with SMTP id 49mr20565616uas.39.1462175622063; Mon, 02 May 2016 00:53:42 -0700 (PDT) Received: by 10.159.34.229 with HTTP; Mon, 2 May 2016 00:53:41 -0700 (PDT) Date: Mon, 2 May 2016 03:53:41 -0400 Message-ID: Subject: zpool import blows up wired vm.kmem_size From: grarpamp To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2016 07:53:43 -0000 10.3-release i386 2GB pentium4 vm.kmem_size=720000000 Needed to keep bumping kmem up to accomodate other zpools. That's the upper limit that will boot on this box. Then got rid of all but one zpool... NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT pool1 232G 228G 3.64G 98% 1.00x ONLINE - pool1 with 6 zfs filesystems with 6+ million inodes. When import attempt, wired mem will hover around 75M for a minute, then jump in a few seconds to about 180M and sit for a few sec, then jump straight to 700+M or so within a second, then the box just sits there with some z-thread[s] stuck in 'kmem a' top state. ARC was only in the low 10M's which sounds fine since no file reads. zpool import -o readonly=on imports through to auto mounting ok. Only read-write blows kmem up and never mounts or returns. Obviously will copy data off it, and off i386. I think it's having problems cleaning up previous writes that hit kmem / powerfail and rebooted. But why the instantaneous jumps in kmem size though? Is this the equivalent of fsck running out of userspace ram on bigfs back in the day, but now zfs in kernel space?