Opened 12 years ago
Last modified 12 years ago
#8392 new bug
bfs errors
Reported by: | jstressman | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | File Systems/BFS | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
I'm having some bfs odd behavior on hrev43844
After looking through my log after another system freeze, I noticed a ton of errors like the following:
bfs: invalid node [0xd7430800] read from offset 518144 (block 7858), inode at 4294 bfs: BPlusTree::_SeekDown() could not open node 518144 bfs: Remove:1958: General system error bfs: invalid node [0xd7430800] read from offset 518144 (block 7858), inode at 4294 bfs: BPlusTree::_SeekDown() could not open node 518144 bfs: Remove:1958: General system error
while using 'checkfs' on the drive, I get the notice in the attached image...
then I looked at the log and saw a ton more various errors and warnings etc. Those are in the attached text file.
This didn't fix the bfs problem either. I still see the same message now each time I try running checkfs.
Attachments (4)
Change History (6)
by , 12 years ago
Attachment: | bfserror1.png added |
---|
by , 12 years ago
Attachment: | bfserrors2.txt added |
---|
comment:1 by , 12 years ago
comment:2 by , 12 years ago
I am attaching a KDL screen shot that I took with my camera, it looks to be related. Hopyfully this information is useful. If it needs a seperate ticket please let me know.
by , 12 years ago
Attachment: | IMG_1432.JPG added |
---|
by , 12 years ago
Attachment: | IMG_1431.JPG added |
---|
Unfortunately, checkfs is not capable of repairing the B+trees yet, so it's normal that those things don't go away; I've just recently implemented verifying the trees, so that you at least know there is something wrong. I'll add a help text explaining this until I find the time to make it able to repair this (which might end up in another tool, though, as it's very time and memory consuming).
The bug itself is most likely a duplicate of the existing open BFS bugs, and is most probably related to one or more bugs in the block cache. Unit tests for that thing are high on my to do list.