2 Mar 2008 13:38
can't schedule work for eX.Y, it's already on!
Hi, I found the following messages in my log: kernel: aoe: aoe_init: AoE v22 initialised. kernel: aoe: 000ea61b8064 e0.2 v400b has 4194304 sectors kernel: aoe: 000ea61b8064 e201.0 v400b has 2097152 sectors kernel: aoe: 000ea61b8064 e9.1 v400b has 8388608 sectors kernel: aoe: 000ea61b8064 e7.1 v400b has 4194304 sectors kernel: aoe: 000ea61b8064 e202.0 v400b has 2097152 sectors kernel: aoe: 000ea61b8064 e1.4 v400b has 2097152 sectors kernel: aoe: 000ea61b8064 e1.1 v400b has 2097152 sectors kernel: aoe: 000ea61b8064 e1.3 v400b has 2097152 sectors kernel: aoe: 000ea61b8064 e1.2 v400b has 2097152 sectors kernel: aoe: 000ea61b8064 e0.1 v400b has 4194304 sectors kernel: aoe: 000ea61b8064 e1.0 v400b has 6291456 sectors kernel: aoe: 000ea61b8064 e101.0 v400b has 2097152 sectors kernel: etherd/e0.2: unknown partition table kernel: etherd/e201.0:<6>aoe: ataid_complete: can't schedule work for e1.3, it's already on! (This really shouldn't happen). kernel: kernel: aoe: ataid_complete: can't schedule work for e9.1, it's already on! (This really shouldn't happen). kernel: kernel: aoe: ataid_complete: can't schedule work for e7.1, it's already on! (This really shouldn't happen). kernel: kernel: aoe: ataid_complete: can't schedule work for e202.0, it's already on! (This really shouldn't happen).(Continue reading)
RSS Feed