#8419 closed bug (duplicate)
PANIC: ASSERT FAILED (/Buildbot/nightly-uploader/workdir/haiku/src/system/kernel/fs/vfs.cpp:950): vnode->ref_count ==0 && vnode->IsBusy(); vnode: 0xd7ea1828
| Reported by: | arfonzo | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | File Systems/BFS | Version: | R1/Development |
| Keywords: | Cc: | SeanCollins | |
| Blocked By: | #3159 | Blocking: | |
| Platform: | All |
Description
I am seeing this panic quite often, hrev43886. Attached are two screenshots of the panic screen.
An example scenario:
- I've tried to clone from git the haiku source following the building guide, 4-5 times now. Each time I get a panic to KDL in git at the same point.
- I did a git clone, on my linux machine. Then I tar'd that up, and wget'd it onto haiku and, same type of panic during un-tar.
- Diver has suggested: there is a bug hiding in bfs/block_cache/some heavy operation triggers it.
- That is consistent with what i'm seeing, although, it seems to be more specific than heavy usage, every single time KDL was brought up was at the same point/file in the git cloning process.
Attachments (2)
Change History (8)
by , 13 years ago
| Attachment: | haiku_kdl_git.png added |
|---|
by , 13 years ago
| Attachment: | haiku_unzip_kdl.png added |
|---|
comment:2 by , 13 years ago
| Cc: | added |
|---|
Could this be because of http://cgit.haiku-os.org/haiku/commit/src/system/kernel/fs/vfs.cpp?id=4bbb2 ?
comment:3 by , 13 years ago
I was able to avoid this panic during my git clone scenario above, by reducing the amount of RAM available to the machine from 4096 down to 512. Not sure if this may be relevant.
comment:5 by , 13 years ago
| Blocked By: | 3159 added |
|---|---|
| Component: | File Systems → File Systems/BFS |
| Resolution: | → duplicate |
| Status: | new → closed |
Duplicate of #3159.
comment:6 by , 13 years ago
Sounds like also running a comprehensive memcheck on the computer would be good just to eliminate bad ram suspicion.
Note:
See TracTickets
for help on using tickets.
look in boot/common/var/log/syslog.I'd like to compared yours to mine, becuase I have about 50 screen shots I have collected this week that are similar, even though they effect different files.