On Nov 8, 11:51am, jaromir.dole...@gmail.com (=?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?=) wrote: -- Subject: Re: ffs_newvnode: inode has non zero blocks
| Yes, that problem is related to the wapbl change. I've committed a bug | fix, so newer kernel shouldn't trigger the panic any more. | | 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. christos