Re: kern/54647: panic: ffs_newvnode: dup alloc ino=2782620

[Larry D'Anna <lawrence_danna%apple.com@localhost>]

The following reply was made to PR kern/54647; it has been noted by GNATS.

From: Larry D'Anna <lawrence_danna%apple.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/54647: panic: ffs_newvnode: dup alloc ino=2782620
Date: Thu, 24 Oct 2019 23:41:01 -0700

 yes, that fixed it. behaves correctly?
 
 > On Oct 24, 2019, at 11:40 PM, Jarom=C3=ADr Dole=C4=8Dek =
 <jaromir.dolecek%gmail.com@localhost> wrote:
 >=20
 > The following reply was made to PR kern/54647; it has been noted by =
 GNATS.
 >=20
 > From: =3D?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=3D?=3D =
 <jaromir.dolecek%gmail.com@localhost>
 > To: "gnats-bugs%NetBSD.org@localhost" <gnats-bugs%netbsd.org@localhost>
 > Cc:=20
 > Subject: Re: kern/54647: panic: ffs_newvnode: dup alloc ino=3D2782620
 > Date: Fri, 25 Oct 2019 08:37:13 +0200
 >=20
 > Le ven. 25 oct. 2019 =3DC3=3DA0 08:35, <lawrence_danna%apple.com@localhost> a =
 =3DC3=3DA9crit =3D
 > :
 >>> How-To-Repeat:
 >> I've got a VM I was using to build LLDB that panics like that every =
 time =3D
 > I start the build back up again.
 >=20
 > Have you tried to fsck the filesystem?
 >=20
 > Jaromir
 >=20