Opened 11 years ago

Closed 2 years ago

#3081 closed bug (not reproducible)

defective vnode

Reported by: donn Owned by: axeld
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
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:

ASSERT FAILED (...bfs/BlockAllocator.cpp:448): !fLargestValid
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.

Change History (3)

comment:1 Changed 11 years ago by axeld

Are you testing on real hardware?

Is this in any way reproducible? I guess you haven't secured a stack trace and poked in the allocation groups a bit using the kernel debugger? :-)

Have you used special vim settings?

comment:2 Changed 11 years ago by donn

Yes, real hardware -

Not reproducible so far, in fact I'm going to be surprised if it happens again. No special vim settings, I just type "vi filename".

comment:3 Changed 2 years ago by axeld

Resolution: not reproducible
Status: newclosed

This ticket does not contain enough information to look into the issue. Please reopen if it happens again.

Note: See TracTickets for help on using tickets.