Hello,

I'm using /dev/md0 as root filesystem. When I boot after / has not been
unmounted, I get the following:

created md0
bind<sda6,1>
bind<sdb6,2>
running: <sdb6><sda6>
now!
sda6's event counter: 00000092
sdb6's event counter: 00000092
md: md0 raid array is not clean.. starting background reconstruction
md0: max total readahead window set to 128k
md0: 1 data-disks, max readahead per data-disk: 128k
raid1: device sdb6 operational as mirror 1
raid1: device sda6 operational as mirror 0
raid1: raid set md0 not clean; reconstructing mirrors
raid1: raid set md0 active with 2 out of 2 mirrors
md: updating md0 RAID superblock on device
sdb6[events: 00000093](write) sdb6's sb offset: 8594624
md: syncing RAID array md0
md: minimum _guaranteed_ reconstruction speed: 100KB/sec.
md: using maximum available idle IO bandwidth for reconstruction.
md: using 128k window.
sda6[events: 00000093](write) sda6's sb offset: 8594624
.
... autorun DONE.
Kernel panic: B_FREE inserted into queues

I can get the system running again when I disconnect one of the disks.
Then I can shutdown, reconnect the second disk, boot and run raidhotadd.

The behaviour is 100% reproducable.
I'm using the 2.2.10 patch with a 2.2.14 kernel. Could that be the
reason?

advTHANXance,

-Malte

--
P.roduces E.normous N.umbers T.hrough I.ncorrect U.nderstanding of M.athematics



Reply via email to