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

#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):

 Still present in r41843 as well.. Got a KDL while browsing in W+ and
 launching BeShare. Tried to 'continue' out of KDL (sometimes works) but it
 just escalated into more panics/failed asserts. So I did a 'reboot', then
 did the exact same thing (launching W+/BeShare) with the same result.. At
 next reboot, the situation was different: the panic would occur just as
 the app_server started, making the system unbootable. After a few minutes
 of experimenting, I found that the "Safe Mode" checkbox in boot menu would
 get me back in Haiku again. At this point I opened a Terminal and did
 this:

 {{{
 ~> checkfs /boot/
 MediaFiles (inode = 2639785), some blocks weren't allocated
 multi_audio_settings (inode = 2639784), some blocks weren't allocated
 syslog (inode = 2097298), some blocks weren't allocated
 syslog.old (inode = 2097362), some blocks weren't allocated, has blocks
 already set
 sshd.pid (inode = 2097299), some blocks weren't allocated
         42173 nodes checked,
         46 blocks not allocated,
         29 blocks already set,
         17 blocks could be freed

         files           38907
         directories     2756
         attributes      329
         attr. dirs      155
         indices         26
 ~>

 }}}

 Then I rebooted sans Safe Mode, and I did get the full-fledged Haiku this
 time, including network, allowing me to post this.

 BFS is still cranky though:

 {{{
 ~> checkfs /boot/
 DriveSetup (inode = 2107402), some blocks weren't allocated
 syslog.old (inode = 2097298), some blocks weren't allocated
         42174 nodes checked,
         29 blocks not allocated,
         0 blocks already set,
         0 blocks could be freed

         files           38908
         directories     2756
         attributes      329
         attr. dirs      155
         indices         26
 ~>
 }}}

 I never get to the point of having a "100% clean" status...

 I expect this will happen again, since I've had it for the last few days..
 So now I use everything in a more 'relaxed' way (no multiples pages in W+
 ..etc) so as to steer clear from this panic as much as possible.

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

Other related posts: