Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Jan 2024 13:28:42 +0000
From:      bugzilla-noreply@freebsd.org
To:        fs@FreeBSD.org
Subject:   [Bug 276341] zfs panic: VERIFY3(rc->rc_count == number) failed
Message-ID:  <bug-276341-3630-4u6frSL3Lt@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-276341-3630@https.bugs.freebsd.org/bugzilla/>
References:  <bug-276341-3630@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276341

--- Comment #5 from Dennis Clarke <dclarke@blastwave.org> ---


I have to wonder if anyone or anything is happening with this
situation as the hits just keep on coming here :=20

root@titan:~ #=20
root@titan:~ # shutdown -p now=20
Shutdown NOW!
shutdown: [pid 4Stopping sshd.
Waiting for PIDS: 4140, 4140.
Stopping cron.
Waiting for PIDS: 4144.
Stopping cirrinad.
Waiting for PIDS: 4076.
Stopping ntpd.
Waiting for PIDS: 4065.
Stopping powerd.
Waiting for PIDS: 4069.
Stopping devd.
Waiting for PIDS: 3809.
Writing entropy file: .
Writing early boot entropy file: .
.
Jan 19 20:40:45 titan syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop... done
Waiting (max 60 seconds) for system process `syncer' to stop...=20
Syncing disks, vnodes remaining... 0 0 0 em0: Link is up 1000 Mbps Full Dup=
lex
em0: link state changed to UP
0 0 0 0 done
All buffers synced.
Swap device mirror/swap removed.
Uptime: 5h7m4s
GEOM_MIRROR: Device swap: provider destroyed.
GEOM_MIRROR: Device swap destroyed.
panic: VERIFY3(rc->rc_count =3D=3D number) failed (872153088 =3D=3D 0)

cpuid =3D 0
time =3D 1705696854
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe03447fa=
af0
vpanic() at vpanic+0x131/frame 0xfffffe03447fac20
spl_panic() at spl_panic+0x3a/frame 0xfffffe03447fac80
zfs_refcount_destroy_many() at zfs_refcount_destroy_many+0xd1/frame
0xfffffe03447facb0
arc_fini() at arc_fini+0x281/frame 0xfffffe03447face0
dmu_fini() at dmu_fini+0x9/frame 0xfffffe03447facf0
spa_fini() at spa_fini+0x36/frame 0xfffffe03447fad30
zfs_kmod_fini() at zfs_kmod_fini+0x7a/frame 0xfffffe03447fad60
zfs_shutdown() at zfs_shutdown+0x2b/frame 0xfffffe03447fad70
kern_reboot() at kern_reboot+0x4f3/frame 0xfffffe03447fadb0
sys_reboot() at sys_reboot+0x3a9/frame 0xfffffe03447fae00
amd64_syscall() at amd64_syscall+0x153/frame 0xfffffe03447faf30
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe03447faf30
--- syscall (55, FreeBSD ELF64, reboot), rip =3D 0x28cdaa, rsp =3D 0x820f19=
5c8, rbp
=3D 0x820f196b0 ---
KDB: enter: panic
[ thread pid 1 tid 100002 ]
Stopped at      kdb_enter+0x33: movq    $0,0xe3a392(%rip)
db> bt
Tracing pid 1 tid 100002 td 0xfffff8010353e000
kdb_enter() at kdb_enter+0x33/frame 0xfffffe03447fac20
spl_panic() at spl_panic+0x3a/frame 0xfffffe03447fac80
zfs_refcount_destroy_many() at zfs_refcount_destroy_many+0xd1/frame
0xfffffe03447facb0
arc_fini() at arc_fini+0x281/frame 0xfffffe03447face0
dmu_fini() at dmu_fini+0x9/frame 0xfffffe03447facf0
spa_fini() at spa_fini+0x36/frame 0xfffffe03447fad30
zfs_kmod_fini() at zfs_kmod_fini+0x7a/frame 0xfffffe03447fad60
zfs_shutdown() at zfs_shutdown+0x2b/frame 0xfffffe03447fad70
kern_reboot() at kern_reboot+0x4f3/frame 0xfffffe03447fadb0
sys_reboot() at sys_reboot+0x3a9/frame 0xfffffe03447fae00
amd64_syscall() at amd64_syscall+0x153/frame 0xfffffe03447faf30
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe03447faf30
--- syscall (55, FreeBSD ELF64, reboot), rip =3D 0x28cdaa, rsp =3D 0x820f19=
5c8, rbp
=3D 0x820f196b0 ---
db>=20

This makes me think that a ZFS ZPOOL scrub is needed at every boot.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-276341-3630-4u6frSL3Lt>