> wapbl_register_inode shouldn't be able to reach that panic... Maybe that's some stack frame optimization.
> it's in wapbl_register_deallocation. Yes, as it says: wapbl_register_deallocation: out of resources > ffs_truncate calls both, but mkdir shouldn't result in things being > released... or so I'd think. But the panics occured during a bunch of mkdirs and ddb says the active process is mkdir! I will try to reproduce these panics on another machine (where downtime is less annoying to my colleagues) but maybe that doesn't work.
