Date: Sun, 04 Jul 2021 12:36:17 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 255979] fsck bad inode number 2 (256) to nextinode Message-ID: <bug-255979-3630-ALds5l1tjl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255979-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-255979-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255979 Gordon Dickens <gordon@dickens.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gordon@dickens.com --- Comment #12 from Gordon Dickens <gordon@dickens.com> --- Has this bug been merged into FreeBSD 13? I ask since I am running stock FreeBSD 13 and I believe that I am seeing this bug in that fsck quits with = the following ending dialog: UNKNOWN FILE TYPE I=3D300955998 UNEXPECTED SOFT UPDATE INCONSISTENCY CLEAR? yes UNKNOWN FILE TYPE I=3D300955999 UNEXPECTED SOFT UPDATE INCONSISTENCY CLEAR? yes CYLINDER GROUP 374: FOUND 80256 VALID INODES INTERNAL ERROR: dups with softupdates UNEXPECTED SOFT UPDATE INCONSISTENCY ** Phase 1b - Rescan For More DUPS fsck_ufs: bad inode number 2 to next inode # So, what do I do to get it fsck finish? Thanks, Gordon Dickens --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255979-3630-ALds5l1tjl>