> | There are some further changes needed to cover a possible dup alloc , > | and to keep the !wapbl case recoverable by fsck. There is ongoing > | discussion on source-changes about that, hope we finalise fix later in > | the week. > > Leaving a filesystem problem committed on head that can cause filesystem > corruption for a week is not considerate to people who use current.
There shouldn't be anything causing filesystem corruption any more. I will resolve this soon. Jaromir
