Date: Mon, 20 Jan 1997 18:09:53 +0100 (MET) From: fj@tfs.com To: FreeBSD-gnats-submit@freebsd.org Subject: bin/2537: Fsck dies with floatingpoint exception Message-ID: <199701201709.SAA28651@schizo.dk.tfs.com> Resent-Message-ID: <199701201720.JAA12762@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 2537
>Category: bin
>Synopsis: Fsck dies with floatingpoint exception
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Jan 20 09:20:01 PST 1997
>Last-Modified:
>Originator: Flemming Jacobsen
>Organization:
>Release: FreeBSD 2.2-RELEASE i386
>Environment:
FreeBSD 2.2 beta, as generated by PHK 970114.
System crashed (bad memory) during intense IO to disk.
>Description:
At reboot automatic fsck failed with the message:
VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE
(setup.c line 384)
Running fsck by hand (on the primary superblock) resulted in a
floatingpoint exception (probably caused by the printf in main.c
with [(float)(sblock.fs_cstotal.cs_nffree * 100) / sblock.fs_dsize)]).
I did retry after setting the npx0 flags to 0x7 - same result.
fsck -b 32 avoided the problem.
>How-To-Repeat:
Good question ;-)
>Fix:
fsck -b {better superblock copy}
Fix fsck to check for divide by zero before trying.
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701201709.SAA28651>