Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 8 Jan 2024 12:15:21 +0100
From:      Lev Serebryakov <lev@FreeBSD.org>
To:        Larry Rosenman <ler@lerctr.org>
Cc:        freebsd-fs <freebsd-fs@freebsd.org>, freebsd-stable <freebsd-stable@freebsd.org>
Subject:   Re: FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.
Message-ID:  <bd8b1191-fa97-4d07-9b84-729bd97e5d5f@FreeBSD.org>
In-Reply-To: <30315c170f7146a5e1a05e4a2eff3d1b@lerctr.org>
References:  <f97d80ee-0b01-4d68-beb5-53e905f0404c@FreeBSD.org> <e74464be-09b6-43e2-9365-7b0271b2d6eb@FreeBSD.org> <cc136316-f285-41bd-8d59-c5adce06e277@quip.cz> <065f4f5c-f38b-45f4-b7e7-5248f871f7e6@FreeBSD.org> <CANCZdfrYCk7%2B6wCALvszmNZOcZeDxxNp%2Bk5PyH%2BTGJZ%2BovsU=Q@mail.gmail.com> <d11ffb2e-0ee8-4c20-b5d9-5ea63463adba@FreeBSD.org> <2f91eeb7-430b-49e2-817b-5acd0f445fe9@FreeBSD.org> <CANCZdfrV7ROiQD-UGAbgydKbYE7jiM_9t9c6n8F79hqq16X0Kg@mail.gmail.com> <962b242d-546f-46ce-9eb2-9bd2a10f4608@FreeBSD.org> <30315c170f7146a5e1a05e4a2eff3d1b@lerctr.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 08.01.2024 1:15, Larry Rosenman wrote:

>>> So, if this is a mirror, then ada0 blank and ada1 with good data, in theory
>>> you should be fine. However, perhaps ZFS is finding that there's an error from
>>> ada1 for real. Does all of ada1 read with a simple dd?
>>   Yep, it is read with dd, I've checked it
>>
>>> Not sure about the losing devices you described later on.
>>>
>>>      > ZFS: i/o error - all block copies unavailable
>>>      > ZFS: can't read MOS of pool zroot
>>>      >
>>>      >
>>>      >   To be honest, I thinks there is something else. Because sequence of events were (sorry, too long, but I think, tht every detail matters here):
>>>
>>>
>>> Yea. There's something that's failing, which zio_read is woefully under reporting for our diagnostic efforts. And/or something is
>>> getting confused by the blank disk and/or the partially resilvered disk.
>>
>>   My theory, that something is confused when one disk is 512/4096 and other is 512/512.
>>
>>   I want to check it on VM, but can not find VM that both (1) allows CMS boot and (2) allows to configure logical and physical sector of virtual HDD.
>>
>>   bhyve could configure sector sizes, but doesn't support BIOS, and VBox and qemu-system can not emulate sector sizes (or I can not google proper configuration).
> 
> When I first saw this, I wonder what ashift is set to on the pool?
   old pool was with ashift=9, but new one is with ashift=12.

-- 
// Lev Serebryakov




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bd8b1191-fa97-4d07-9b84-729bd97e5d5f>