NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

kern/39295: file systems corrupted after a crash with wapbl

>Number:         39295
>Category:       kern
>Synopsis:       file systems corrupted after a crash with wapbl
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 05 16:15:00 +0000 2008
>Originator:     Alan Barrett
>Release:        NetBSD 4.99.71
Not much
System: NetBSD 4.99.71
Architecture: i386
Machine: i386
        After almost any system crash in which some fiel systems were
        mounted with wapbl logging, the file systems are corrupted.

        The usual "fsck -p" performed during boot decides not to fix the
        file systems, printing "file system is journaled; not checking".

        Soon after the fils systems are nmounted, the corrupted file
        system causes a crash.
        mount some file systems with ffs+wapbl.

        have a kernel panic for almost any reason.


        observe that "fsck -p" doesn't clean the file systems.

        the boot continues.

        this crash occurs before the boot has finished:

        panic: kernel diagnostic assertion "!(bp->b_oflags & BO_DELWRI)"
        failed, file .../vfs_wapbl.c, line 890
        db{0}> bt
        breakpoint ...
        panic ...
        __kernassert ...
        wapbl_add_buf ...
        bdwrite ...
        ffs_blkfree ...
        ffs_truncate ...
        ufs_inactive ...
        VOP_INACTIVE ...
        vrelel ...
        vrele ...
        layer_reclaim ...
        VOP_RECLAIM ...
        vclean ...
        vrelel ...
        vrele_thread ...


Home | Main Index | Thread Index | Old Index