From nobody Tue Jul 22 17:46:11 2025 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 4bml7S3FLhz5pwt6 for ; Tue, 22 Jul 2025 17:46:28 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ej1-f41.google.com (mail-ej1-f41.google.com [209.85.218.41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bml7P4n77z3FBB for ; Tue, 22 Jul 2025 17:46:25 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.218.41 as permitted sender) smtp.mailfrom=asomers@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none) Received: by mail-ej1-f41.google.com with SMTP id a640c23a62f3a-ae0d7b32322so903518366b.2 for ; Tue, 22 Jul 2025 10:46:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753206383; x=1753811183; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=1a8FWMr6ly4WRKUmSTLw/PIQSVUG3j+8WBoeuUnB9Fw=; b=F41L2WdAzTmFqPGij9EhM3rK1d2lH/akWpC9JZlrKoRdE9Gh9Ju0BRlQCJQUxjMj9o 8Wjm51+6nacJeLWcD+yVHhWZIC1eJFQvNyzuCoYAIfSlx5MQCQY3D7/h28tJRtvt1ino C//4cB/PdonNt1fi1j51v0Zul7Y/YWWHqXD0gGITK3020PfBzM2lK0tffcpRVULK90je 1rkkor47ZCs+8E7ZIgBC5RHSTf0IrRj6nLaPUHC7f5FjA6zM0+UxVLuNHamt9bmAmjsx b6oX60lb6XFNjzF/6f5RHY/ayQ9p6FhCgSUsc2SCE4TpjCS25OleEKPWI2TuwqklQlNN eLUg== X-Gm-Message-State: AOJu0YzLbiE8pmab5iuU7LBtEJ0E9Y76DHJm/BgxTPqoIWnHH2lMrfhZ YLWRk5lDT9BaaHuUY/sv+KE7V3FIme+eK6bTGIcIc6SB5Aib1B2m7p7O0DqaC9I2AiSuVvjgDEL 8xEzs28NPVLYtqPqaliCj3T5qoIPMhfkzUw== X-Gm-Gg: ASbGncsXVCsRd2GmYBsabRw36dYNTv/E+MXU8QYzLoHGom9DVuJLS+wWcw8dHONZquT WlcK4fO9jh80ynl7ZZLS90jjpiodhTnFwqPMCx2W6vyXLFO8s7o/plG57DSgHaWK0VZU1d3bHNc Qds2HfiMtj+fKbRUWuq6Uymzls6WCGv71wrBgiXP/wNCXs48zXLYI4amfYR3liwYSmVFRZgTSHJ Q+CK+4= X-Google-Smtp-Source: AGHT+IGyykF0ZR7HXXWaXRCe6ia4ko7qNeTKitFcAOJEQiyRvFlT7d2Ne4qC79vQqlprJY1oS1HZozAuV7lpfjAFB+4= X-Received: by 2002:a17:906:8f12:b0:ae3:64e2:c1e with SMTP id a640c23a62f3a-ae9cdda3d23mr2698356566b.10.1753206382863; Tue, 22 Jul 2025 10:46:22 -0700 (PDT) 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 References: In-Reply-To: From: Alan Somers Date: Tue, 22 Jul 2025 11:46:11 -0600 X-Gm-Features: Ac12FXxTfUkW1-naEwinlD2dpqUhVRAYr8Uurbv1LvXc610mK8lZ_Ix-kQa0gdc Message-ID: Subject: Re: zfs panic VERIFY3U To: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000ab2b39063a882bca" X-Spamd-Result: default: False [0.40 / 15.00]; NEURAL_SPAM_LONG(0.99)[0.994]; NEURAL_HAM_SHORT(-0.79)[-0.793]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_SPAM_MEDIUM(0.20)[0.199]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; RWL_MAILSPIKE_GOOD(-0.10)[209.85.218.41:from]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; RCVD_IN_DNSWL_NONE(0.00)[209.85.218.41:from]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DOM_EQ_FROM_DOM(0.00)[]; R_DKIM_NA(0.00)[]; FREEFALL_USER(0.00)[asomers]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4bml7P4n77z3FBB X-Spamd-Bar: / --000000000000ab2b39063a882bca Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jul 22, 2025 at 6:50=E2=80=AFAM void wrote: > On Tue, Jul 22, 2025 at 02:38:52AM +0100, void wrote: > >On Tue, Jul 22, 2025 at 02:28:19AM +0100, void wrote: > >> > >>zpool import causes the following output at the console: > >>https://void.f-m.fm.user.fm/panic/zpool-broken.png > > > >agh, should read http://void.f-m.fm.user.fm/panic/zpool-broken.png > >*not* https, sorry. > > booting without zfs.ko loaded, then building kernel from > main-stabweek-2025-Jul > rebooting again then loading zfs.ko then zpool import -a went normally > ald zpool status showed an unavailable disk in the raidz2 pool. > -- > From the panic, it looks like your vdev is smaller than what is recorded in the label. I can think of a few reasons why that might be: * It's a VM, and you shrunk the size of the VM's disk. ZFS can't tolerate that. * You shrunk the size of the disk using some exotic SCSI commands. * The disk is broken in such a way that it reports mediasize 0. I've seen that happen. You can check with "geom disk list". * ZFS found an old label. Perhaps it dates from before you expanded a vdev. You might've pulled out a disk, then expanded the other disks in that RAID or mirror, then reinserted the old disk. These problems are annoying, but solvable. This is also one case where you might get different results if you import during boot vs after boot. Is this still a problem for you, or is it all solved? --000000000000ab2b39063a882bca Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Jul 22, 2025 at 6:50=E2=80=AFAM void = <void@f-m.fm> wrote:
On Tue, Jul 22, 2025 at 02:38= :52AM +0100, void wrote:
>On Tue, Jul 22, 2025 at 02:28:19AM +0100, void wrote:
>>
>>zpool import causes the following output at the console:
>>https://void.f-m.fm.user.fm/panic/zpool-b= roken.png
>
>agh, should read http://void.f-m.fm.user.fm/pan= ic/zpool-broken.png
>*not* https, sorry.

booting without zfs.ko loaded, then building kernel from main-stabweek-2025= -Jul
rebooting again then loading zfs.ko then zpool import -a went normally
ald zpool status showed an unavailable disk in the raidz2 pool.
--

From the panic, it looks like your = vdev is smaller than what is recorded in the label.=C2=A0 I can think of a = few reasons why that might be:
* It's a VM, and you shrunk th= e size of the VM's disk.=C2=A0 ZFS can't tolerate that.
*= You shrunk the size of the disk using some exotic SCSI commands.
* The disk is broken in such a way that it reports mediasize 0.=C2=A0 I= 9;ve seen that happen.=C2=A0 You can check with "geom disk list".=
* ZFS found an old label.=C2=A0 Perhaps it dates from before you= expanded a vdev.=C2=A0 You might've pulled out a disk, then expanded t= he other disks in that RAID or mirror, then reinserted the old disk.=C2=A0 = These problems are annoying, but solvable.=C2=A0 This is also one case wher= e you might get different results if you import during boot vs after boot.<= /div>

Is this still a problem for you, or is it all solv= ed?
--000000000000ab2b39063a882bca--