Opened 10 years ago

Closed 11 days ago

#2537 closed bug (invalid)

Ftp crash causes a deadlock in journal area

Reported by: emitrax Owned by: axeld
Priority: normal Milestone: R1
Component: File Systems/BFS Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Ftp crash while doing a mget of a few files, and (perhaps it's just a coincidence) while trying to open one of them already downloaded. After the crash, the journal area is locked.

Unfortunately I forgot to get the backtrace of this thread.

THREAD: 0x913c0800
id:                 9 (0x9)
name:               "block notifier/writer"
all_next:           0x00000000
team_next:          0x9136a000
q_next:             0x800f79c0
priority:           5 (next 5)
state:              ready
next_state:         ready
cpu:                0x00000000
sig_pending:        0x0 (blocked: 0x0)
in_kernel:          1
waiting for:        fault_handler:      0x00000000
args:               0x00000000 0x00000000
entry:              0x80029fdc
team:               0x90b7b000, "kernel_team"
  exit.sem:         34
  exit.status:      0x0 (No error)
  exit.reason:      0x0
  exit.signal:      0x0
  exit.waiters:
kernel_stack_area:  95
kernel_stack_base:  0x8015d000
user_stack_area:    -1
user_stack_base:    0x00000000
user_local_storage: 0x00000000
kernel_errno:       0x0 (No error)
kernel_time:        7691481
user_time:          0
flags:              0x0
architecture dependant section:
    esp: 0x8016084c
    ss: 0x00000010
    fpu_state at 0x913c0b80
kdebug> mutex 0x90b8c2d4
mutex 0x90b8c2d4:
  name:            bfs journal
  flags:           0x0
  holder:          9
  waiting threads: 85 300 203 192 200

Change History (3)

comment:1 Changed 8 years ago by Coldfirex

emitrax: is this still an issue?

comment:2 Changed 16 months ago by diver

Component: - GeneralFile Systems/BFS

comment:3 Changed 11 days ago by waddlesplash

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.