Date: Sat, 2 May 2020 10:03:40 +0200 (CEST) From: =?UTF-8?Q?Trond_Endrest=C3=B8l?= <trond.endrestol@ximalas.info> To: Ireneusz Pluta <ipluta@wp.pl> Cc: freebsd-questions@freebsd.org Subject: Re: How to get rid of an unavailable pool? Message-ID: <alpine.BSF.2.22.395.2005020959190.91211@enterprise.ximalas.info> In-Reply-To: <32264a1f-3bcf-9d74-603d-c201bffd256c@wp.pl> References: <32264a1f-3bcf-9d74-603d-c201bffd256c@wp.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2 May 2020 06:15+0200, Ireneusz Pluta wrote: > Hi group, > > (Sorry if this post appears twice. The first one, initially sent from another > email account, does not seem to appear.) > > I have (or rather had) a pool like this: > > $ sudo zpool status -v t > pool: t > state: UNAVAIL > status: One or more devices are faulted in response to IO failures. > action: Make sure the affected devices are connected, then run 'zpool clear'. > see: http://illumos.org/msg/ZFS-8000-HC > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > t UNAVAIL 0 0 0 > mirror-0 UNAVAIL 0 0 0 > 4304281762335857859 REMOVED 0 0 0 was /dev/da5 > 1909766900844089131 REMOVED 0 0 0 was /dev/da10 > > errors: Permanent errors have been detected in the following files: > > <metadata>:<0x0> > <metadata>:<0x1b> > t:<0x0> > > That was a temporary test pool. I forgot to destroy or at least export the > pool before pulling these da5 and da10 drives out of the drivebay of the > server. Now it can't be exported or destroyed, the respective zpool operations > hust hang. How to get rid now of this pool, preferably without reboot? The da5 > and da10 are no longer available to be put back, as they have been already > moved elsewhere, and are now part of another pool. > > I guess the pool got stuck at the time of running > /etc/periodic/security/100.chksetuid, when find operation within it tried to > traverse into the mountpoint of the pool. > > The system is FreeBSD 11.2. > > Thanks > > Irek The pool might still be listed in /boot/zfs/zpool.cache. The only way I can think of to get rid of the old pool, is to delete this file and reboot. If you have more pools than your root pool, you should reboot to singleuser mode, mount the root fs read-write, import the remaining pools, and either exit the SUS shell or reboot. -- Trond. From owner-freebsd-questions@freebsd.org Sat May 2 08:28:02 2020 Return-Path: <owner-freebsd-questions@freebsd.org> Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 43EDF2C82B9 for <freebsd-questions@mailman.nyi.freebsd.org>; Sat, 2 May 2020 08:28:02 +0000 (UTC) (envelope-from kuku@kukulies.org) Received: from mail.kukulies.org (mail.kukulies.org [116.203.115.43]) by mx1.freebsd.org (Postfix) with ESMTP id 49Dj1F41TXz3Qb8 for <freebsd-questions@freebsd.org>; Sat, 2 May 2020 08:28:01 +0000 (UTC) (envelope-from kuku@kukulies.org) Received: from localhost (localhost [127.0.0.1]) by mail.kukulies.org (Postfix) with ESMTP id 576F110276A for <freebsd-questions@freebsd.org>; Sat, 2 May 2020 10:28:00 +0200 (CEST) Received: from mail.kukulies.org ([127.0.0.1]) by localhost (mail.kukulies.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EWNKgqaLXnXf for <freebsd-questions@freebsd.org>; Sat, 2 May 2020 10:28:00 +0200 (CEST) Received: from [192.168.178.78] (p57A1FCC2.dip0.t-ipconnect.de [87.161.252.194]) by mail.kukulies.org (Postfix) with ESMTPSA id F0062102769 for <freebsd-questions@freebsd.org>; Sat, 2 May 2020 10:27:59 +0200 (CEST) To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> From: "Christoph P.U. Kukulies" <kuku@kukulies.org> Subject: sym0 weirdness Message-ID: <373ced34-1fe5-c385-e2c4-20cc6f46d9f0@kukulies.org> Date: Sat, 2 May 2020 10:27:58 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 X-Rspamd-Queue-Id: 49Dj1F41TXz3Qb8 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of kuku@kukulies.org has no SPF policy when checking 116.203.115.43) smtp.mailfrom=kuku@kukulies.org X-Spamd-Result: default: False [2.78 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; DMARC_NA(0.00)[kukulies.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(0.29)[ipnet: 116.203.0.0/16(3.01), asn: 24940(-1.53), country: DE(-0.02)]; NEURAL_SPAM_MEDIUM(0.30)[0.304,0]; NEURAL_SPAM_LONG(0.88)[0.883,0]; MIME_HTML_ONLY(0.20)[]; R_SPF_NA(0.00)[]; TO_DN_EQ_ADDR_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:~]; ASN(0.00)[asn:24940, ipnet:116.203.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; RECEIVED_SPAMHAUS_PBL(0.00)[194.252.161.87.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10] MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions <freebsd-questions.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>; List-Post: <mailto:freebsd-questions@freebsd.org> List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 02 May 2020 08:28:02 -0000
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.22.395.2005020959190.91211>