ZFS panic on shutdown

53314e34d5e8e7f781ab990805b22f7a56bc0580 (freebsd/main) Author: Christos Margiolis Date: Sat Oct 19 16:34:27 2024 +0200 i observed this ZFS panic during shutdown: panic: VERIFY(avl_is_empty(&sk->sk_dsl_keys)) failed i cannot reproduce this reliably and have rebooted several times after this with

Another ZFS Panic -- buffer modified while frozen

A different panic on a different amd64 machine also running poudriere but building amd64 packages. Exmh was just started, displaying back to my laptop at the time of panic. panic: buffer modified while frozen! cpuid = 1 time = 1693417762 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_

Re: ZFS: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed

On 27/05/2023 16:30, Graham Perrin wrote: Three panics with c2c9ac88c2bb (2023-05-26, 1400089): … Martin, if you'd like to take , please go ahead. Thanks OpenPGP_signature Description: OpenPGP digital signature

ZFS: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed

Three panics with c2c9ac88c2bb (2023-05-26, 1400089): Dumptime: 2023-05-27 03:17:16 +0100 Dumptime: 2023-05-27 03:41:03 +0100 Dumptime: 2023-05-27 14:03:32 +0100 Are they symptomatic of

Re: ZFS PANIC: HELP.

On 02/27/2022 3:58 pm, Mark Johnston wrote: On Sun, Feb 27, 2022 at 01:16:44PM -0600, Larry Rosenman wrote: On 02/26/2022 11:08 am, Larry Rosenman wrote: > On 02/26/2022 10:57 am, Larry Rosenman wrote: >> On 02/26/2022 10:37 am, Juraj Lutter wrote: On 26 Feb 2022, at 03:03, Larry Rosenman

Re: ZFS PANIC: HELP.

On Sun, Feb 27, 2022 at 01:16:44PM -0600, Larry Rosenman wrote: > On 02/26/2022 11:08 am, Larry Rosenman wrote: > > On 02/26/2022 10:57 am, Larry Rosenman wrote: > >> On 02/26/2022 10:37 am, Juraj Lutter wrote: > On 26 Feb 2022, at 03:03, Larry Rosenman wrote: > I'm running this script:

Re: ZFS PANIC: HELP.

On 2/27/22 16:09, Larry Rosenman wrote: On 02/27/2022 3:03 pm, Michael Butler wrote: [ cc list trimmed ] On 2/27/22 14:16, Larry Rosenman wrote: I was able to export the rest of the datasets, and re-install 14-CURRENT from a recent snapshot, and restore the datasets I care about. I'm now

Re: ZFS PANIC: HELP.

On 02/27/2022 3:03 pm, Michael Butler wrote: [ cc list trimmed ] On 2/27/22 14:16, Larry Rosenman wrote: I was able to export the rest of the datasets, and re-install 14-CURRENT from a recent snapshot, and restore the datasets I care about. I'm now seeing: mfi0: IOCTL 0x40086481 not handle

Re: ZFS PANIC: HELP.

[ cc list trimmed ] On 2/27/22 14:16, Larry Rosenman wrote: I was able to export the rest of the datasets, and re-install 14-CURRENT from a recent snapshot, and restore the datasets I care about. I'm now seeing: mfi0: IOCTL 0x40086481 not handled mfi0: IOCTL 0x40086481 not handled mfi0: IOC

Re: ZFS PANIC: HELP.

On 02/26/2022 11:08 am, Larry Rosenman wrote: On 02/26/2022 10:57 am, Larry Rosenman wrote: On 02/26/2022 10:37 am, Juraj Lutter wrote: On 26 Feb 2022, at 03:03, Larry Rosenman wrote: I'm running this script: #!/bin/sh for i in $(zfs list -H | awk '{print $1}') do FS=$1 FN=$(echo ${FS} | s

Re: ZFS PANIC: HELP.

On 02/26/2022 10:57 am, Larry Rosenman wrote: On 02/26/2022 10:37 am, Juraj Lutter wrote: On 26 Feb 2022, at 03:03, Larry Rosenman wrote: 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}@RE

Re: ZFS PANIC: HELP.

On 02/26/2022 10:37 am, Juraj Lutter wrote: On 26 Feb 2022, at 03:03, Larry Rosenman wrote: 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 l...@freenas.lerctr.org cat -

Re: ZFS PANIC: HELP.

Quoting Larry Rosenman (from Fri, 25 Feb 2022 20:03:51 -0600): 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

Re: ZFS PANIC: HELP.

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 dat

Re: ZFS PANIC: HELP.

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 eve

Re: ZFS PANIC: HELP.

On 02/24/2022 8:07 pm, Larry Rosenman wrote: On 02/24/2022 1:27 pm, Larry Rosenman wrote: On 02/24/2022 10:48 am, Rob Wing wrote: even with those set, I still get the panid. :( Let me see if I can compile a 14 non-INVARIANTS kernel on the 13-REL system. UGH. I chroot'd to the pool, and

Re: ZFS PANIC: HELP.

On 02/24/2022 1:27 pm, Larry Rosenman wrote: On 02/24/2022 10:48 am, Rob Wing wrote: even with those set, I still get the panid. :( Let me see if I can compile a 14 non-INVARIANTS kernel on the 13-REL system. UGH. I chroot'd to the pool, and built a no invariants kernel. It booted an

Re: ZFS PANIC: HELP.

On 02/24/2022 10:48 am, Rob Wing wrote: Yes, I believe so. On Thu, Feb 24, 2022 at 7:42 AM Larry Rosenman wrote: On 02/24/2022 10:36 am, Rob Wing wrote: You might try setting `sysctl vfs.zfs.recover=1` and `sysctl vfs.zfs.spa.load_verify_metadata=0`. I had a similar error the other day

Re: ZFS PANIC: HELP.

Yes, I believe so. On Thu, Feb 24, 2022 at 7:42 AM Larry Rosenman wrote: > On 02/24/2022 10:36 am, Rob Wing wrote: > > You might try setting `sysctl vfs.zfs.recover=1` and `sysctl > vfs.zfs.spa.load_verify_metadata=0`. > > I had a similar error the other day (couple months ago). The best I did >

Re: ZFS PANIC: HELP.

On 02/24/2022 10:36 am, Rob Wing wrote: You might try setting `sysctl vfs.zfs.recover=1` and `sysctl vfs.zfs.spa.load_verify_metadata=0`. I had a similar error the other day (couple months ago). The best I did was being able to import the pool read only. I ended up restoring from backup.

Re: ZFS PANIC: HELP.

You might try setting `sysctl vfs.zfs.recover=1` and `sysctl vfs.zfs.spa.load_verify_metadata=0`. I had a similar error the other day (couple months ago). The best I did was being able to import the pool read only. I ended up restoring from backup. On Thu, Feb 24, 2022 at 7:30 AM Alexander Motin

Re: ZFS PANIC: HELP.

On 02/24/2022 10:29 am, Alexander Motin wrote: On 24.02.2022 10:57, Larry Rosenman wrote: On 02/23/2022 9:27 pm, Larry Rosenman wrote: It crashes just after root mount (this is the boot pool and only pool on the system), seeL https://www.lerctr.org/~ler/14-BOOT-Crash.png Where do I go from he

Re: ZFS PANIC: HELP.

On 24.02.2022 10:57, Larry Rosenman wrote: On 02/23/2022 9:27 pm, Larry Rosenman wrote: It crashes just after root mount (this is the boot pool and only pool on the system), seeL https://www.lerctr.org/~ler/14-BOOT-Crash.png Where do I go from here? I see 2 ways: 1) Since it is only an asser

Re: ZFS PANIC: HELP.

On 02/23/2022 9:27 pm, Larry Rosenman wrote: On 02/23/2022 9:15 pm, Alexander Motin wrote: On 23.02.2022 22:01, Larry Rosenman wrote: On 02/23/2022 8:58 pm, Alexander Motin wrote: On 23.02.2022 21:52, Larry Rosenman wrote: On 02/23/2022 8:41 pm, Alexander Motin wrote: Hi Larry, The panic yo

Re: ZFS PANIC: HELP.

On 02/23/2022 9:15 pm, Alexander Motin wrote: On 23.02.2022 22:01, Larry Rosenman wrote: On 02/23/2022 8:58 pm, Alexander Motin wrote: On 23.02.2022 21:52, Larry Rosenman wrote: On 02/23/2022 8:41 pm, Alexander Motin wrote: Hi Larry, The panic you are getting is an assertion, enabled by kern

Re: ZFS PANIC: HELP.

On 23.02.2022 22:01, Larry Rosenman wrote: On 02/23/2022 8:58 pm, Alexander Motin wrote: On 23.02.2022 21:52, Larry Rosenman wrote: On 02/23/2022 8:41 pm, Alexander Motin wrote: Hi Larry, The panic you are getting is an assertion, enabled by kernel built with INVARIANTS option.  On 13 you may

Re: ZFS PANIC: HELP.

On 02/23/2022 8:58 pm, Alexander Motin wrote: On 23.02.2022 21:52, Larry Rosenman wrote: On 02/23/2022 8:41 pm, Alexander Motin wrote: Hi Larry, The panic you are getting is an assertion, enabled by kernel built with INVARIANTS option.  On 13 you may just not have that debugging enabled to hit

Re: ZFS PANIC: HELP.

On 23.02.2022 21:52, Larry Rosenman wrote: On 02/23/2022 8:41 pm, Alexander Motin wrote: Hi Larry, The panic you are getting is an assertion, enabled by kernel built with INVARIANTS option.  On 13 you may just not have that debugging enabled to hit the issue.  But that may be only a consequence

Re: ZFS PANIC: HELP.

On 02/23/2022 8:41 pm, Alexander Motin wrote: Hi Larry, The panic you are getting is an assertion, enabled by kernel built with INVARIANTS option. On 13 you may just not have that debugging enabled to hit the issue. But that may be only a consequence. Original problem I guess in possibly corru

Re: ZFS PANIC: HELP.

Hi Larry, The panic you are getting is an assertion, enabled by kernel built with INVARIANTS option. On 13 you may just not have that debugging enabled to hit the issue. But that may be only a consequence. Original problem I guess in possibly corrupted ZFS intent log records (or false posi

ZFS PANIC: HELP.

've got my main dev box that crashes on 14 with the screen shot at https://www.lerctr.org/~ler/14-zfs-crash.png. Booting from a 13-REL USB installer it imports and scrubs. Ideas? I can either video conference with shared screen or give access to the console via my Dominion KVM. Any help/i

Re: zfs panic when 'make buildworld buildkernel'

Please try https://svnweb.freebsd.org/changeset/base/366717 On 10/15/20, YAMAMOTO Shigeru wrote: > > Thank you for your help. > > after > https://svnweb.freebsd.org/base?view=revision&revision=366685 > > I update kernel and try to 'make buildworld buildkernel'. > > 1st time, I can finished 'make

Re: zfs panic when 'make buildworld buildkernel'

Thank you for your help. after https://svnweb.freebsd.org/base?view=revision&revision=366685 I update kernel and try to 'make buildworld buildkernel'. 1st time, I can finished 'make buildworld buildkernel'. 2nd time, panic ``` [root@jenkins-02 ~]# uname -a FreeBSD jenkins-02.current.os-hack

Re: zfs panic when 'make buildworld buildkernel'

On 10/13/20, Mateusz Guzik wrote: > On 10/13/20, YAMAMOTO Shigeru wrote: >> >> Hi, >> >> I try to 'make buildworld buildkernel' at full ZFS environment. >> But I can't finished buildworld/buildkernel without panic. >> Anyone have same trouble? >> >> uname -a: >> ``` >> FreeBSD jenkins-02.current.

Re: zfs panic when 'make buildworld buildkernel'

On 10/13/20, YAMAMOTO Shigeru wrote: > > Hi, > > I try to 'make buildworld buildkernel' at full ZFS environment. > But I can't finished buildworld/buildkernel without panic. > Anyone have same trouble? > > uname -a: > ``` > FreeBSD jenkins-02.current.os-hackers.jp 13.0-CURRENT FreeBSD 13.0-CURRENT

zfs panic when 'make buildworld buildkernel'

Hi, I try to 'make buildworld buildkernel' at full ZFS environment. But I can't finished buildworld/buildkernel without panic. Anyone have same trouble? uname -a: ``` FreeBSD jenkins-02.current.os-hackers.jp 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r366657: Tue Oct 13 13:07:15 JST 2020 r...@jenkins

Re: ZFS Panic: Current: r354843: panic: solaris assert: error || lr->lr_length <= size, file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: 1324

On 11/19/19 3:51 PM, Larry Rosenman wrote: Ideas?  Core *IS* available, and I can give access. Unread portion of the kernel message buffer: panic: solaris assert: error || lr->lr_length <= size, file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: 1324 cpuid = 20 t

ZFS Panic: Current: r354843: panic: solaris assert: error || lr->lr_length <= size, file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: 1324

Ideas? Core *IS* available, and I can give access. Unread portion of the kernel message buffer: panic: solaris assert: error || lr->lr_length <= size, file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: 1324 cpuid = 20 time = 1574159903 KDB: stack backtrace: db_tr

Re: ZFS panic at boot when mounting root on r330386

On 05/03/2018 02:59, Bryan Drewery wrote: >> panic: solaris assert: refcount_count(&spa->spa_refcount) > spa->spa_minref >> || MUTEX_HELD(&spa_namespace_lock), file: >> /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa_misc.c, line: 952 >> cpuid = 10 >> time = 1520207367 >> KDB: stack b

ZFS panic at boot when mounting root on r330386

> panic: solaris assert: refcount_count(&spa->spa_refcount) > spa->spa_minref > || MUTEX_HELD(&spa_namespace_lock), file: > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa_misc.c, line: 952 > cpuid = 10 > time = 1520207367 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_

random ZFS panic...

Was rebooting my laptop, and got the following: trivet dumped core - see /var/crash/vmcore.0 Wed Mar 2 06:09:19 CST 2016 FreeBSD trivet 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r296287: Tue Mar 1 19:13:37 CST 2016 root@trivet:/usr/obj/usr/src/sys/GENERIC amd64 panic: from debugger GNU gdb

Re: ZFS panic

CC+= swills On 9/17/15, Oliver Pinter wrote: > Hi All! > > We got this panic on modified FreeBSD (we not touched the ZFS part). > > panic: solaris assert: error || lr->lr_length <= zp->z_blksz, file: > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, > line: 1355 > cpuid = 6 >

ZFS panic

Hi All! We got this panic on modified FreeBSD (we not touched the ZFS part). panic: solaris assert: error || lr->lr_length <= zp->z_blksz, file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: 1355 cpuid = 6 KDB: stack backtrace: #0 0x80639527 at kdb_backtrace+0

Re: [ZFS] [panic] Fatal trap 12: page fault while in kernel mode.

В Tue, 10 Feb 2015 22:01:29 +0200 Ivan Klymenko пишет: > I do not know the conditions - it just happened. > > http://pastebin.com/BASJB599 next http://pastebin.com/hY8GYpjd ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/

Re: [ZFS] [panic] Fatal trap 12: page fault while in kernel mode.

В Tue, 10 Feb 2015 22:01:29 +0200 Ivan Klymenko пишет: > I do not know the conditions - it just happened. > > http://pastebin.com/BASJB599 > ___ > freebsd...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscri

[ZFS] [panic] Fatal trap 12: page fault while in kernel mode.

I do not know the conditions - it just happened. http://pastebin.com/BASJB599 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

On 20/07/14 16:03, Larry Rosenman wrote: > > panic: solaris assert: !(zio->io_flags & ZIO_FLAG_DELEGATED), file: > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c, line: > 2874 > This was fixed by r268980. Florian signature.asc Description: OpenPGP digital signature

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I think this is my stupid. Feeling ashamed. Please try r268980+ and report back if it's fixed or not, thanks! Cheers, -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJTzihjAAoJEJW2GBstM+ns2esP/3zfORqtE11QeveWI8wBzHav Pl4A3V8kgi8FHP8m33gim1yAERpqf2+Wg

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

On 2014-07-21 00:24, Florian Smeets wrote: On 21/07/14 01:46, Steven Hartland wrote: - Original Message - From: "Larry Rosenman" To: "Steven Hartland" Cc: ; Sent: Monday, July 21, 2014 12:22 AM Subject: Re: [ZFS][PANIC] Solaris Assert/zio.c:2548 On 2014

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

On 21/07/14 01:46, Steven Hartland wrote: > - Original Message - From: "Larry Rosenman" > To: "Steven Hartland" > Cc: ; > Sent: Monday, July 21, 2014 12:22 AM > Subject: Re: [ZFS][PANIC] Solaris Assert/zio.c:2548 > > >> On 2014-07-2

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

- Original Message - From: "Dan Mack" To: "Steven Hartland" Cc: ; ; "Larry Rosenman" Sent: Monday, July 21, 2014 2:29 AM Subject: Re: [ZFS][PANIC] Solaris Assert/zio.c:2548 On Mon, 21 Jul 2014, Steven Hartland wrote: I just updated to I think 26

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

- Original Message - From: "Dan Mack" To: "Steven Hartland" Cc: ; ; "Larry Rosenman" Sent: Monday, July 21, 2014 2:29 AM Subject: Re: [ZFS][PANIC] Solaris Assert/zio.c:2548 On Mon, 21 Jul 2014, Steven Hartland wrote: I just updated to I think 26

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

On Mon, 21 Jul 2014, Steven Hartland wrote: I just updated to I think 268921 earlier today and this is the first time I've had a panic (HEAD-268921 that is) I'll try to get some more data if I can get it back up and running. That doesn't look like a related trace tbh. Regards Steve Aft

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

On Mon, 21 Jul 2014, Steven Hartland wrote: - Original Message - From: "Dan Mack" I think I may have hit the same problem; I'm going to stay connected to the console and see if it happens again; this is what I see currently with the back-trace: db> bt Tracing pid 0 tid 100070 td 0xf

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

On Mon, 21 Jul 2014, Steven Hartland wrote: - Original Message - From: "Larry Rosenman" To: "Steven Hartland" Cc: ; Sent: Monday, July 21, 2014 12:22 AM Subject: Re: [ZFS][PANIC] Solaris Assert/zio.c:2548 On 2014-07-20 18:21, Steven Hartland wrote: Can you t

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

- Original Message - From: "Dan Mack" I think I may have hit the same problem; I'm going to stay connected to the console and see if it happens again; this is what I see currently with the back-trace: db> bt Tracing pid 0 tid 100070 td 0xf8000e088920 kdb_enter() at kdb_enter+0x3

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

On 2014-07-20 18:46, Steven Hartland wrote: - Original Message - From: "Larry Rosenman" To: "Steven Hartland" Cc: ; Sent: Monday, July 21, 2014 12:22 AM Subject: Re: [ZFS][PANIC] Solaris Assert/zio.c:2548 On 2014-07-20 18:21, Steven Hartland wrote: Can you t

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

- Original Message - From: "Larry Rosenman" To: "Steven Hartland" Cc: ; Sent: Monday, July 21, 2014 12:22 AM Subject: Re: [ZFS][PANIC] Solaris Assert/zio.c:2548 On 2014-07-20 18:21, Steven Hartland wrote: Can you try reverting r265321 and see if you stil

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

On 2014-07-20 18:21, Steven Hartland wrote: Can you try reverting r265321 and see if you still see the same crash? Regards Steve I'll do the revert, but it's been a ONE TIME hit. There was a followup to mine with a reproducible poudriere crash like mine. -- Larry Rosenman

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

Can you try reverting r265321 and see if you still see the same crash? Regards Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr.

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

"Steven Hartland" Cc: ; Sent: Sunday, July 20, 2014 8:20 PM Subject: Re: [ZFS][PANIC] Solaris Assert/zio.c:2548 On 2014-07-20 14:18, Steven Hartland wrote: Can you provide the details of the zio which caused the panic? Also does any of your pools support trim? No, on the trim

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

enman" To: ; Sent: Sunday, July 20, 2014 3:03 PM Subject: [ZFS][PANIC] Solaris Assert/zio.c:2548 Got the following panic overnight (I think while a nightly rsync was running): Dump header from device /dev/gpt/swap0 Architecture: amd64 Architecture Version: 2 Dump Length: 8122101760

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

Can you provide the details of the zio which caused the panic? Also does any of your pools support trim? Regards Steve - Original Message - From: "Larry Rosenman" To: ; Sent: Sunday, July 20, 2014 3:03 PM Subject: [ZFS][PANIC] Solaris Assert/zio.c:2548 Got the

Re: [ZFS][PANIC] Solaris Assert/zio.c:2548

On 20/07/14 16:03, Larry Rosenman wrote: > Panic String: solaris assert: !(zio->io_flags & ZIO_FLAG_DELEGATED), > file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c, > line: 2874 > > Unread portion of the kernel message buffer: panic: solaris assert: > !(zio->io_flags & ZIO_FLA

[ZFS][PANIC] Solaris Assert/zio.c:2548

Got the following panic overnight (I think while a nightly rsync was running): Dump header from device /dev/gpt/swap0 Architecture: amd64 Architecture Version: 2 Dump Length: 8122101760B (7745 MB) Blocksize: 512 Dumptime: Sun Jul 20 03:22:18 2014 Hostname: borg.lerctr.org Magic: Free

Re: ZFS panic in -CURRENT

(follow up below) On 04/01/2014 06:57, R. Tyler Croy wrote: On Tue, 01 Apr 2014 09:41:45 +0300 Andriy Gapon wrote: on 01/04/2014 02:22 R. Tyler Croy said the following: Bumping this with more details On Fri, 28 Mar 2014 09:53:32 -0700 R Tyler Croy wrote: Apologies for the rough format he

Re: ZFS panic in -CURRENT

on 02/04/2014 19:48 R. Tyler Croy said the following: > On Wed, 02 Apr 2014 09:58:37 +0300 > Andriy Gapon wrote: > >> on 01/04/2014 16:57 R. Tyler Croy said the following: >>> On Tue, 01 Apr 2014 09:41:45 +0300 >>> Andriy Gapon wrote: >>> on 01/04/2014 02:22 R. Tyler Croy said the following

Re: ZFS panic in -CURRENT

On Wed, 02 Apr 2014 09:58:37 +0300 Andriy Gapon wrote: > on 01/04/2014 16:57 R. Tyler Croy said the following: > > On Tue, 01 Apr 2014 09:41:45 +0300 > > Andriy Gapon wrote: > > > >> on 01/04/2014 02:22 R. Tyler Croy said the following: > ... > >>> Also in addition to the photo from before of t

Re: ZFS panic in -CURRENT

on 01/04/2014 16:57 R. Tyler Croy said the following: > On Tue, 01 Apr 2014 09:41:45 +0300 > Andriy Gapon wrote: > >> on 01/04/2014 02:22 R. Tyler Croy said the following: ... >>> Also in addition to the photo from before of the panic, here's >>> another reproduction photo: >>>

Re: ZFS panic in -CURRENT

On Tue, 01 Apr 2014 09:41:45 +0300 Andriy Gapon wrote: > on 01/04/2014 02:22 R. Tyler Croy said the following: > > Bumping this with more details > > > > On Fri, 28 Mar 2014 09:53:32 -0700 > > R Tyler Croy wrote: > > > >> Apologies for the rough format here, I had to take a picture of > >> thi

Re: ZFS panic in -CURRENT

on 01/04/2014 02:22 R. Tyler Croy said the following: > Bumping this with more details > > On Fri, 28 Mar 2014 09:53:32 -0700 > R Tyler Croy wrote: > >> Apologies for the rough format here, I had to take a picture of this >> failure because I didn't know what else to do. >> >>

Re: ZFS panic in -CURRENT

Bumping this with more details On Fri, 28 Mar 2014 09:53:32 -0700 R Tyler Croy wrote: > Apologies for the rough format here, I had to take a picture of this > failure because I didn't know what else to do. > > > > I'm building off of the Gi

ZFS panic in -CURRENT

Apologies for the rough format here, I had to take a picture of this failure because I didn't know what else to do. I'm building off of the GitHub freebsd.git mirror here, and the latest commit in the tree is neel@'s "Add an ioctl to suspend

Re: ZFS panic (dn->dn_datablkshift != 0) with r256304 and send/recv

On Mon, 14 Oct 2013, Andriy Gapon wrote: on 14/10/2013 03:34 Keith White said the following: I get the following assert failure with a recent current: panic: solaris assert: dn->dn_datablkshift != 0, file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_tx.c, line

Re: ZFS panic (dn->dn_datablkshift != 0) with r256304 and send/recv

on 14/10/2013 03:34 Keith White said the following: > I get the following assert failure with a recent current: > > panic: solaris assert: dn->dn_datablkshift != 0, file: > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_tx.c, > line: 638 Please see https://www.illum

ZFS panic (dn->dn_datablkshift != 0) with r256304 and send/recv

I get the following assert failure with a recent current: panic: solaris assert: dn->dn_datablkshift != 0, file: /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/dmu_tx.c, line: 638 # uname -a FreeBSD freebsd10 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r256304: Thu Oct 10

Re: ZFS panic with r255937

On Thu, 3 Oct 2013, Andriy Gapon wrote: on 02/10/2013 20:59 Keith White said the following: On Wed, 2 Oct 2013, Andriy Gapon wrote: on 30/09/2013 02:11 kwh...@site.uottawa.ca said the following: Sorry, debugging this is *way* beyond me. Any hints, patches to try? Please share the stack tr

Re: ZFS panic with r255937

on 02/10/2013 20:59 Keith White said the following: > On Wed, 2 Oct 2013, Andriy Gapon wrote: > >> on 30/09/2013 02:11 kwh...@site.uottawa.ca said the following: >>> Sorry, debugging this is *way* beyond me. Any hints, patches to try? >> >> Please share the stack trace. >> >> -- >> Andriy Gapon

Re: ZFS panic with r255937

On Wed, 2 Oct 2013, Andriy Gapon wrote: on 30/09/2013 02:11 kwh...@site.uottawa.ca said the following: Sorry, debugging this is *way* beyond me. Any hints, patches to try? Please share the stack trace. -- Andriy Gapon There's now a pr for this panic: kern/182570 Here's the stack trace:

Re: ZFS panic with r255937

on 30/09/2013 02:11 kwh...@site.uottawa.ca said the following: > Sorry, debugging this is *way* beyond me. Any hints, patches to try? Please share the stack trace. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/m

ZFS panic with r255937

I get the following reproducible panic when doing a zfs send -R | zfs recv of a well churned file system (snapshots of the ports tree before and after libiconv update) running a recent current: panic: solaris assert: dn->dn_maxblkid == 0 && (BP_IS_HOLE(&dn->dn_phys->dn_blkptr[0]) || dnode_block_fr

Re: ZFS panic with concurrent recv and read-heavy workload

On Fri, Jun 03, 2011 at 03:03:56AM -0400, Nathaniel W Filardo wrote: > I just got this on another machine, no heavy workload needed, just booting > and starting some jails. Of interest, perhaps, both this and the machine > triggering the below panic are SMP V240s with 1.5GHz CPUs (though I will >

Re: ZFS panic with concurrent recv and read-heavy workload

I just got this on another machine, no heavy workload needed, just booting and starting some jails. Of interest, perhaps, both this and the machine triggering the below panic are SMP V240s with 1.5GHz CPUs (though I will confess that the machine in the original report may have had bad RAM). I hav

ZFS panic with concurrent recv and read-heavy workload

When racing two workloads, one doing > zfs recv -v -d testpool and the other > find /testpool -type f -print0 | xargs -0 sha1 I can (seemingly reliably) trigger this panic: panic: Lock buf_hash_table.ht_locks[i].ht_lock not exclusively locked @ /usr/src/sys/modules/zfs/../../cddl/contrib/openso

Re: zfs panic

On 2010-06-23, ben wilber wrote: > > > panic: _sx_xlock_hard: recursed on non-recursive sx > > > buf_hash_table.ht_locks[i].ht_lock @ > > > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/c > > > ommon/fs/zfs/arc.c:1626 > > > > Any chance to obtain a backtrace for the panic? > > >Fr

Re: zfs panic

On Wed, Jun 23, 2010 at 10:01 PM, ben wilber wrote: > On Wed, Jun 23, 2010 at 01:47:33PM -0700, Xin LI wrote: >> > >> > panic: _sx_xlock_hard: recursed on non-recursive sx >> > buf_hash_table.ht_locks[i].ht_lock @ >> > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/c >> > ommon/fs/z

Re: zfs panic

On Wed, Jun 23, 2010 at 01:47:33PM -0700, Xin LI wrote: > > > > panic: _sx_xlock_hard: recursed on non-recursive sx > > buf_hash_table.ht_locks[i].ht_lock @ > > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/c > > ommon/fs/zfs/arc.c:1626 > > Any chance to obtain a backtrace for the

Re: zfs panic

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Ben, On 2010/06/23 09:44, ben wilber wrote: > Hi, > > Since at least r208174, I've been getting the following panic every few days > on > my fairly heavily loaded amd64 machine: > > panic: _sx_xlock_hard: recursed on non-recursive sx > buf_h

zfs panic

Hi, Since at least r208174, I've been getting the following panic every few days on my fairly heavily loaded amd64 machine: panic: _sx_xlock_hard: recursed on non-recursive sx buf_hash_table.ht_locks[i].ht_lock @ /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/c ommon/fs/zfs/arc.c:1

ZFS panic import

Hi, I have (had), a freebsd 8.0 release-p2 running a zfs poll with raidz, 3 disks 250gb SATA and 1 disk IDE... OK... this was running for a while without problem, but, some day ago, with a power outage the zfs don't import anymore. All the system was in the ZFS, so, i had to use a fixit cd for tr