|Reported by:||donn||Owned by:||axeld|
|Has a Patch:||no||Platform:||All|
Coincidentally with upgrade to hrev28520, vim caused a panic whenever it tried to write to .viminfo, specifically the panic occurred during new_vnode() and claimed that a vnode already existed. new_vnode was called indirectly by bfs_create().
checkfs report on .viminfo said "some blocks weren't allocated"
When I deleted .viminfo (via "rm"), I got another panic:
|start + length <= fLargestStart|
in <bfs> AllocationGroup::Free()
But the directory entry was gone, and the checkfs problem is gone. (I do have other checkfs problems - directory with "blocks already set", and related files that can't be opened.)
This problem occurred while checking on #3010, where I promised I would report it. If anything like this happens again, I'll add it to this ticket.