[haiku-bugs] Re: [Haiku] #5262: PANIC: vnode 3:7895866 already exists (node = 0xe0044000, vnode->node = 0xe008bbf4)!

  • From: "ttcoder" <trac@xxxxxxxxxxxx>
  • Date: Tue, 28 Jun 2011 17:45:39 -0000

#5262: PANIC: vnode 3:7895866 already exists (node = 0xe0044000, vnode->node =
0xe008bbf4)!
--------------------------------+----------------------------
   Reporter:  justeco           |      Owner:  axeld
       Type:  bug               |     Status:  new
   Priority:  critical          |  Milestone:  R1
  Component:  File Systems/BFS  |    Version:  R1/Development
 Resolution:                    |   Keywords:
 Blocked By:                    |   Blocking:
Has a Patch:  0                 |   Platform:  x86
--------------------------------+----------------------------

Comment (by ttcoder):

 Thanks for feedback; some more input from me, in order of relevance: 1)
 I've found a sure-fire way to corrupt the FS! 2) checkfs seems to have
 restored stuff, oddly.

 And 3) I'm definitely looking forward upgrading and doing an Initialize on
 that partition :-) .. Waiting for RAW images to be available again, so
 that I can upgrade to my spare Haiku partition "for free" (ISOs are for
 burning to a CD but I want to do this on the cheap *g*) (and VMWare and
 anyboot images cannot be double-clicked and mounted apparently).

 Here's the odd "clean bill of health" I got after a few iterations over
 the last few days (I have a very solid and enjoyable system these days, so
 long as I remember to skip 1).. ):

 {{{
 ~> checkfs /boot
         44547 nodes checked,
         0 blocks not allocated,
         0 blocks already set,
         0 blocks could be freed

         files           40738
         directories     3261
         attributes      349
         attr. dirs      173
         indices         26
 }}}

 Not sure if this is reliable or if there could be nasties hidden in an
 inode somewhere though.

 As to 1), I'll file a proper ticket after confirming (or maybe update this
 ticket, not sure whether the symptoms warrant a new ticket or not), but
 I'm 99% sure of the following:
 - if I use the deskbar's Shutdown/Power off menu item, Haiku shuts down
 without doing a BFS 'sync' (or whatever it is called), resulting in
 trouble at next cold start: at a minimum I get checkfs shouting about
 TrackerSettings, tracker_shelf ..etc (i.e. the kind of things that are
 written to disk when you shutdown) but most times I get dropped to KDL
 with the 'vnode PANIC', and it takes 2 "continue" to resume bootup.
 - if I use "Restart System" and THEN press the off switch on the tower (at
 e.g. BIOS POST time) then at next boot Haiku is 100% good.

 I guess this occurs only on my PC, others would have caught this thing
 before if their system failed to "sync' at shutdown.. So gotta confirm
 first.

 Also noted that several fixes to e.g. the VM system have been done since
 41843, I'm eager to upgrade to them... (will keep watching haiku-files...)

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/5262#comment:7>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts:

  1. Home
  2. haiku-bugs
  3. Archive
  4. 06-2011