misc/47231: WAPBL dangers

[jakllsch%kollasch.net@localhost]

>Number:         47231
>Category:       misc
>Synopsis:       crash or power loss during cvs update on WAPBL-enabled volume 
>results in near-irreparable damage to CVS metadata.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    misc-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Nov 21 17:20:01 +0000 2012
>Originator:     Jonathan A. Kollasch
>Release:        NetBSD 6.99.15
>Organization:
>Environment:
        
        
System: NetBSD xenotaph.kollasch.net 6.99.15 NetBSD 6.99.15 (GENERIC) #81: Tue 
Nov 13 18:46:31 CST 2012 
jakllsch%xenotaph.kollasch.net@localhost:/local/jakllsch/NetBSD/obj-amd64/sys/arch/amd64/compile/GENERIC
 amd64
Architecture: x86_64
Machine: amd64
>Description:
Crash or power loss during cvs update on WAPBL-enabled volume results in
near-irreparable damage to CVS working copy metadata.
>How-To-Repeat:
Stop kernel (via debugger/crash/power-loss) while cvs update is running
on a larger tree (such as pkgsrc) within a WAPBL/log-enabled file system.
When the machine comes up again (and journal replayed), try
to run the cvs update again and note how confused it is.
>Fix:
Unknown, but workaround would be to disable WAPBL.

>Unformatted: