Date: Fri, 09 Sep 2016 14:40:09 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 211823] [patch] fsck_ffs incorrectly failing in check_cgmagic Message-ID: <bug-211823-8-s7DWy7j357@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211823-8@https.bugs.freebsd.org/bugzilla/> References: <bug-211823-8@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=3D211823 --- Comment #6 from Christian Heckendorf <heckendorfc@gmail.com> --- Both variables hold the same value in their internal representation (0xcc00) but cg_old_niblk overflows into negative values due to type limitations that fs_ipg doesn't have. Clearly check_cgmagic() thinks the fs data is invalid = yet somehow OpenBSD fsck thinks it works and the filesystem in general seems to work fine on both OS, at least from a basic usage standpoint (I haven't loo= ked into anything more than basic I/O and whether fsck says clean or dirty). Is this check in check_cgmagic meant to compare internal representations or th= eir signed/unsigned integer values? Is general compatibility between UFS in OpenBSD and FreeBSD purely accident= al? If so, I'll drop the issue. --=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-211823-8-s7DWy7j357>