[ENBD] fr1 hangs when trying to access raid device..
Peter T. Breuer
enbd@lists.community.tummy.com
Wed, 5 Feb 2003 19:22:51 +0100 (MET)
"A month of sundays ago Peter T. Breuer wrote:"
> But what stops you trying it on 240 like that? I'll try it on 9.
Yes, I just tried it wth major=9 and it works (only change being the
req=CURRENT replacement that I suggested earlier).
209 19:16 sudo insmod ./fr1.o major=9
210 19:16 cat /proc/fr1stat
211 19:16 sudo vi /etc/raidtab
212 19:16 sudo mkraid --dangerous-no-resync --really-force /dev/md0
213 19:16 cat /proc/fr1stat
214 19:17 sync
215 19:17 head -10c /dev/md0
216 19:17 sudo head -10c /dev/md0
217 19:17 sudo dd if=/dev/zero of=/dev/md0 count=10 &
dmesg output shows some diagnostics ..
fr1 ioctl 800c0910
fr1 ioctl 800c0910
fr1 ioctl 40480923
fr1 ioctl 40140921
fr1 hotadd component 07:00[0] to device 0
fr1 added new device 07:00 to cb424800 with err 0
fr1 ioctl 40140921
fr1 hotadd component 07:01[1] to device 0
fr1 added new device 07:01 to cb424800 with err 0
fr1 ioctl 400c0930
promoted request c6b9bf60
promoted request c6b9bc60
promoted request c6b9b960
promoted request c6b9b660
promoted request c6b9b360
fr1stat shows what it should ..
betty:/usr/oboe/ptb/lang/c/fr1/fr1-1.0% cat /proc/fr1stat
Personalities : [raid1]
read_ahead 4 sectors
fr10 : active fr1 [dev 07:00][0] [dev 07:01][1]
2048 blocks
So I would guess that there is probably a procedural problem in your
experiment. Possibly you are not loading the code that you think you
are?
(I am running SMP, but with one processor, 2.4.19).
Peter