Date: Sun, 27 Feb 2022 18:16:53 -0600 From: Larry Rosenman <ler@lerctr.org> To: Mark Johnston <markj@freebsd.org> Cc: Freebsd current <freebsd-current@freebsd.org> Subject: Re: ZFS PANIC: HELP. Message-ID: <20d8b59ddfa82275ac771a50921f9300@lerctr.org> In-Reply-To: <Yhv0EhJ4gq%2BlxBlD@nuc> References: <CAF3%2Bn_cevarxBYMJ5%2BGeTex6C%2Be-A79TbpDL-Pd7jsWPKfu=SA@mail.gmail.com> <36d3896af19acc4fdd1712822ba9d420@lerctr.org> <9f6a8ad62fc0dbd6f3a19c7d695bd302@lerctr.org> <c2fb568ba91c61974cb439f6bda1aec3@lerctr.org> <20220225091120.Horde.76VjoVNtr5BsqAw_5ftjpRZ@webmail.leidinger.net> <d1db05269410cb5d8b0ba00b264d26e9@lerctr.org> <04CB94C0-93FE-402B-A24E-1BDAC0D87C5D@lutter.sk> <8df623691922973b5e9b8609d78c4cfa@lerctr.org> <85057850abd46331c95b9a2f3a0c07d8@lerctr.org> <740a16472bb1073174efa709f795896c@lerctr.org> <Yhv0EhJ4gq%2BlxBlD@nuc>
next in thread | previous in thread | raw e-mail | index | archive | 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 <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.
per advice from markj@ I deleted the /{etc,boot}/zfs/zpool.cache files,
and this issue went
away. Stale cache files which are no longer needed.
--
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20d8b59ddfa82275ac771a50921f9300>