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
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
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
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
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
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
'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
On Wed, Feb 23, 2022 at 12:25:24PM -0500, Alexander Motin wrote:
> On 22.02.2022 19:00, Konstantin Belousov wrote:
> > On Tue, Feb 22, 2022 at 06:53:09PM -0500, Alexander Motin wrote:
> > > On 22.02.2022 18:41, Konstantin Belousov wrote:
> > > > On Tue, Feb 22, 2022 at 06:38:24PM -0500, Alexander M
