Re: ZFS PANIC: HELP.
- Reply: Larry Rosenman : "Re: ZFS PANIC: HELP."
- In reply to: Larry Rosenman : "Re: ZFS PANIC: HELP."
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 27 Feb 2022 21:58:42 UTC
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 <ler@lerctr.org> 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 > >>>> ler@freenas.lerctr.org cat - \> $FN > >>>> done > >>>> > >>>> > >>>> > >>> I’d put, like: > >>> > >>> echo ${FS} > >>> > >>> before “sudo zfs send”, to get at least a bit of a clue on where it > >>> can get to. > >>> > >>> otis > >>> > >>> > >>> — > >>> Juraj Lutter > >>> otis@FreeBSD.org > >> I just looked at the destination to see where it died (it did!) and I > >> bectl destroy'd the > >> BE that crashed it, and am running a new scrub -- we'll see whether > >> that was sufficient. > >> > >> Thanks, all! > > Well, it was NOT sufficient.... More zfs export fun to come :( > > 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: IOCTL 0x40086481 not handled > mfi0: IOCTL 0x40086481 not handled > pid 48 (zpool), jid 0, uid 0: exited on signal 6 > mfi0: IOCTL 0x40086481 not handled > mfi0: IOCTL 0x40086481 not handled > mfi0: IOCTL 0x40086481 not handled > mfi0: IOCTL 0x40086481 not handled > pid 54 (zpool), jid 0, uid 0: exited on signal 6 > > On boot. Ideas? That ioctl is DIOCGMEDIASIZE, i.e., something is asking /dev/mfi0, the controller device node, about the size of a disk. Presumably this is the result of some kind of misconfiguration somewhere, and /dev/mfid0 was meant instead.