From nobody Sat Feb 26 02:03:51 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 8930A19CF389 for ; Sat, 26 Feb 2022 02:03:56 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.lerctr.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4K59174Pkhz4nW1; Sat, 26 Feb 2022 02:03:55 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=ler2019; h=Content-Type:Message-ID:References:In-Reply-To:Subject:Cc:To: From:Date:MIME-Version:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=HxfOZSVIxhhoYc6J4FcK74owBsjp14CKDKJjIWDQFxQ=; b=naTHpb6klnQ6zUxX/+VzvaY4vn uprGPL1dZCb7ZVpfoRqx1yvMOPcGSmu28NoJWZKoYj8BjHoOGWBXHwoU3iMaHZK0Snq7iaslBuaX5 6KbO55aPpJ3ZBV+EhwVq91UPGGP/aDtJZBQq/mBQguTvrbpIZWvuz2w+ImqtCAwHjU90btgDMQWhb kKrOdjCgAkdVVg6JO0umIhQOELw1fC10gU152OL6AivkSQF9l7otDbtfJAzjVWI1mpyUZF+U/yjz+ GVEPApPhCqQUPdBBEPpqlCNGi7I43eGd8hdkIyUlg1EaT5oPlPHqIx3yHpNkgQHSVvH6PnPsoNo8T FRc8VpUQ==; Received-SPF: pass (thebighonker.lerctr.org: domain of lerctr.org designates 2001:470:1f0f:3ad:bb:dcff:fe50:d900 as permitted sender) client-ip=2001:470:1f0f:3ad:bb:dcff:fe50:d900; envelope-from=ler@lerctr.org; helo=webmail.lerctr.org; Received: from thebighonker.lerctr.org ([2001:470:1f0f:3ad:bb:dcff:fe50:d900]:60374 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.95 (FreeBSD)) (envelope-from ) id 1nNmR5-000CL5-TX; Fri, 25 Feb 2022 20:03:51 -0600 Received: from 2600:1700:210:b18f:97c:f609:c6e2:df80 by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Fri, 25 Feb 2022 20:03:51 -0600 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Date: Fri, 25 Feb 2022 20:03:51 -0600 From: Larry Rosenman To: Alexander Leidinger Cc: Rob Wing , Alexander Motin , Freebsd current Subject: Re: ZFS PANIC: HELP. In-Reply-To: <20220225091120.Horde.76VjoVNtr5BsqAw_5ftjpRZ@webmail.leidinger.net> References: <07c0c9c34b4a4133acab597c96867d27@lerctr.org> <95c7c326-e2f9-6e66-7b97-b9fb2671f4ad@FreeBSD.org> <1b6b2017ba69e6fda1ca237c3016ac61@lerctr.org> <6182c57bf1859482e72af78037c399e4@lerctr.org> <7abcbe88-446f-44b9-c3a7-0997d3430b57@FreeBSD.org> <2bc12c9ee3e6dd71b65079116ff2b845@lerctr.org> <5930f3d2b71c0932f903bb5b88a3c87d@lerctr.org> <36d3896af19acc4fdd1712822ba9d420@lerctr.org> <9f6a8ad62fc0dbd6f3a19c7d695bd302@lerctr.org> <20220225091120.Horde.76VjoVNtr5BsqAw_5ftjpRZ@webmail.leidinger.net> Message-ID: X-Sender: ler@lerctr.org Content-Type: multipart/alternative; boundary="=_c7968c98c9db15b5ca066756c67c3273" X-Rspamd-Queue-Id: 4K59174Pkhz4nW1 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=lerctr.org header.s=ler2019 header.b=naTHpb6k; dmarc=pass (policy=none) header.from=lerctr.org; spf=pass (mx1.freebsd.org: domain of ler@lerctr.org designates 192.147.25.65 as permitted sender) smtp.mailfrom=ler@lerctr.org X-Spamd-Result: default: False [-2.80 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[lerctr.org:s=ler2019]; FREEFALL_USER(0.00)[ler]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[lerctr.org:+]; DMARC_POLICY_ALLOW(-0.50)[lerctr.org,none]; SUBJ_ALL_CAPS(1.20)[16]; MLMMJ_DEST(0.00)[freebsd-current]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:8166, ipnet:192.147.25.0/24, country:US]; FREEMAIL_CC(0.00)[gmail.com,freebsd.org]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --=_c7968c98c9db15b5ca066756c67c3273 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On 02/25/2022 2:11 am, Alexander Leidinger wrote: > Quoting Larry Rosenman (from Thu, 24 Feb 2022 20:19:45 > -0600): > >> I tried a scrub -- it panic'd on a fatal double fault. >> >> Suggestions? > > The safest / cleanest (but not fastest) is data export and pool > re-creation. If you export dataset by dataset (instead of recursively > all), you can even see which dataset is causing the issue. In case this > per dataset export narrows down the issue and it is a dataset you don't > care about (as in: 1) no issue to recreate from scratch or 2) there is > a backup available) you could delete this (or each such) dataset and > re-create it in-place (= not re-creating the entire pool). > > Bye, > Alexander. > > http://www.Leidinger.net Alexander@Leidinger.net: PGP > 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP > 0x8F31830F9F2772BF I'm running this script: #!/bin/sh for i in $(zfs list -H | awk '{print $1}') do FS=$1 FN=$(echo ${FS} | sed -e s@/@_@g) sudo zfs send -vecLep ${FS}@REPAIR_SNAP | ssh ler@freenas.lerctr.org cat - \> $FN done How will I know a "Problem" dataset? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 --=_c7968c98c9db15b5ca066756c67c3273 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

On 02/25/2022 2:11 am, Alexander Leidinger wrote:

Quoting Larry Rosenman <ler@lerctr.org> (from Thu, 24 Feb 2022 20:19:45 -0600):

I tried a scrub -- it panic'd on a fatal double fault. 

Suggestions?

The safest / cleanest (but not fastest) is data export and pool re-creat= ion. If you export dataset by dataset (instead of recursively all), you can= even see which dataset is causing the issue. In case this per dataset expo= rt narrows down the issue and it is a dataset you don't care about (as in: = 1) no issue to recreate from scratch or 2) there is a backup available) you= could delete this (or each such) dataset and re-create it in-place (=3D no= t re-creating the entire pool).

Bye,
Alexander.

http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2= 772BF
http://www.FreeBSD.org    netchild@FreeBSD.org  : P= GP 0x8F31830F9F2772BF

I'm running this script:
#!/bin/sh
for i in $(zfs list -H | aw= k '{print $1}')
do
  FS=3D$1
  FN=3D$(echo ${FS} |= sed -e s@/@_@g)
  sudo zfs send -vecLep ${FS}@REPAIR_SNAP | ssh = ler@freenas.lerctr.org cat - \> $FN
done


How will I know a "Problem" dataset?


= -- 
Larry Rosenman     &n= bsp;            = ;   http://www.lerctr.org/~ler
Phone: +1 = 214-642-9640           &n= bsp;     E-Mail: ler@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106=
--=_c7968c98c9db15b5ca066756c67c3273--