From owner-freebsd-fs@freebsd.org Mon Jun 27 15:21:12 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 B8D68B84957 for ; Mon, 27 Jun 2016 15:21:12 +0000 (UTC) (envelope-from holger@freyther.de) Received: from gandharva.secretlabs.de (gandharva.secretlabs.de [IPv6:2a01:4f8:161:8201::2:4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8564624D8 for ; Mon, 27 Jun 2016 15:21:12 +0000 (UTC) (envelope-from holger@freyther.de) Received: from [192.168.61.98] (p57B9824C.dip0.t-ipconnect.de [87.185.130.76]) by gandharva.secretlabs.de (Postfix) with ESMTPSA id 0F803814BE; Mon, 27 Jun 2016 15:21:08 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Deadlock in zpool import with degraded pool From: Holger Freyther In-Reply-To: <8a4cb87252c04ebfbf71451c5dc1a41e@exch2-4.slu.se> Date: Mon, 27 Jun 2016 17:21:07 +0200 Cc: "freebsd-fs@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <9DF3E719-5184-419E-B81A-599D5ECCD969@freyther.de> References: <8a4cb87252c04ebfbf71451c5dc1a41e@exch2-4.slu.se> To: =?utf-8?Q?Karli_Sj=C3=B6berg?= X-Mailer: Apple Mail (2.3124) 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, 27 Jun 2016 15:21:12 -0000 > On 26 Jun 2016, at 19:28, Karli Sj=C3=B6berg = wrote: >=20 Hi, > That's your problem right there; dedup! You need to throw more RAM = into it until the destroy can complete. If the mobo is 'full', you need = new/other hw to cram more RAM into or you can kiss your data goodbye. = I've been in the exact same situation as you are now so I sympathize:( did you look at it further? * Why does it only start after I zfs destroyed something? The dedup = hash/table/??? grows by that? * Why a plain dead-lock and no panic? * Is there an easy way to see how much RAM is needed? (In the end I can = use Linux/KVM with RAM backed in a file/disk and just wait...) * Would you know if zpool import -o readonly avoids loading/building = that big table? =46rom common sense this block table would only be = needed on write to map from checksum to block? kind regards holger=