[haiku-bugs] Re: [Haiku] #6034: BFS Panics
- From: "AGMS" <trac@xxxxxxxxxxxx>
- Date: Wed, 22 Oct 2014 18:41:32 -0000
#6034: BFS Panics
--------------------------------+-----------------------
Reporter: bryanv | Owner: axeld
Type: bug | Status: reopened
Priority: critical | Milestone: R1
Component: File Systems/BFS | Version: R1/alpha2
Resolution: | Keywords: Panics
Blocked By: | Blocking:
Has a Patch: 0 | Platform: x86
--------------------------------+-----------------------
Comment (by AGMS):
That last panic report is mostly due to something else - mounting a raw
disk image file on ext4 containing a BeOS disk volume seems to corrupt the
kernel memory list. Guess loopback mounting doesn't work well with those
file systems. Tried again with a real disk partition for the BeOS BFS
source data.
But I still get bugs copying e-mail to Haiku. It looks like something is
wrong with BPlusTree or the way it writes data (caching?). It manages to
mangle the attribute index while copying files (just did a copyattr -r -d
-v of a few thousand old e-mails). The destination was a freshly
formatted install of hrev48061, with mail indices created. This is what
the log looks like, mixed with output from the file copying and a later
checkfs:
/boot/home/Mail Archives/Champlain Speaker/Mail System Error - Returned
Mail 20070912213055 Mail Administrator
/boot/home/Mail Archives/Champlain Speaker/Mail System Error - Returned
Mail 20071126212315 Mail Administrator
KERN: bfs: invalid node [0xf3923400] read from offset 343040 (block 8103),
inode at 5588
KERN: bfs: KERN: BPlusTree::_SeekDown() could not open node 343040, inode
5588
KERN: bfs: Insert:1692: General system error
KERN: bfs: Update:279: General system error
KERN: bfs: invalid node [0xf3923400] read from offset 343040 (block 8103),
inode at 5588
KERN: bfs: KERN: BPlusTree::_SeekDown() could not open node 343040, inode
5588
KERN: bfs: Insert:1692: General system error
KERN: bfs: Update:279: General system error
[zillions more of the same, a pause, then the file copying continues, then
it happens again]
~> checkfs /boot/
MAIL:to (inode = 5588), invalid b+tree
Recreating broken index b+trees...
10264 nodes checked,
0 blocks not allocated,
0 blocks already set,
0 blocks could be freed
files 10105
directories 161
attributes 39
attr. dirs 28
indices 24
direct block runs 10456 (2.10 GiB)
indirect block runs 362 (in 9 array blocks, 5.94 GiB)
double indirect block runs 0 (in 0 array blocks, 0 bytes)
~> KERN: bfs: invalid node [0xf3923400] read from offset 343040 (block
8103), inode at 5588
KERN: inode 5588: node at 343040 could not be read: Bad data
KERN: inode 5588: node at 6144 has wrong left link 306176, expected 38912!
KERN: inode 5588: node at 30720 has wrong right link 249856, expected
344064!
KERN: inode 5588: node at 344064 has wrong left link 253952, expected
30720!
KERN: inode 5588: visited 234 from 351 nodes.
KERN: bfs: ReadAttribute:1070: No such file or directory
KERN: Last message repeated 987 times.
--
Ticket URL: <https://dev.haiku-os.org/ticket/6034#comment:15>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
