[email protected]
[Top] [All Lists]

bin/43336: fsck wapbl assertion failure after crash

Subject: bin/43336: fsck wapbl assertion failure after crash
From: Hauke Fath
Date: Fri, 21 May 2010 16:05:00 +0000 UTC
>Number:         43336
>Category:       bin
>Synopsis:       fsck wapbl assertion failure after crash
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri May 21 16:05:00 +0000 2010
>Originator:     Hauke Fath
>Release:        NetBSD 5.0_STABLE
>Organization:
-- 
     The ASCII Ribbon Campaign                    Hauke Fath
()     No HTML/RTF in email             Institut für Nachrichtentechnik
/\     No Word docs in email                     TU Darmstadt
     Respect for open standards              Ruf +49-6151-16-3281
>Environment:
        
        
System: NetBSD Gstoder 5.0_STABLE NetBSD 5.0_STABLE (P4W) #0: Mon Mar 8 
18:05:33 CET 2010 
[email protected]:/var/obj/netbsd-builds/5/i386/sys/arch/i386/compile/P4W i386
Architecture: i386
Machine: i386
>Description:

        During reboot from a kernel panic, my netbsd-5 system dropped
        to single-user, fsck(8) died with the following wapbl
        assertion failure:

<http://www.spg.tu-darmstadt.de/~hf/netbsd/netbsd-5-wapbl.jpg>

        I've seen this problem three times so far. The only way out
        appears to be a 'tunefs -l 0 /dev/rwd0[aefg...]' followed by
        'mount -a' and 'shutdown -r now'.

>How-To-Repeat:

        On a netbsd-5 machine with file-systems mount(8)ed '-o log'
        run into a kernel panic that dumps core and reboots. Find that
        fsck(8) will not.

>Fix:
        For a workaround, see above.

        Manuel Bouyer suggested changing the assertion into a warning,
        so that fsck can clean up the log.

>Unformatted:
        
        

<Prev in Thread] Current Thread [Next in Thread>