I just managed to type 0 instead of linear in my /etc/raidtab. - Doing:
raid0run resulted in below BUG.
I know this is a user error since after replacing 0 with linear it all
worked fine, but is it really necessary to get a BUG in this case?
Probably the answer is yes but I thought I would post it just in case...
bind<hdb7,1>
nonpersistent superblock ...
md0: WARNING: hdb9 appears to be on the same physical disk as hdb7. True
protection against single-disk failure might be compromised.
bind<hdb9,2>
nonpersistent superblock ...
hdb9's event counter: 00000000
hdb7's event counter: 00000000
md0 stopped.
unbind<hdb9,1>
export_rdev(hdb9)
unbind<hdb7,0>
export_rdev(hdb7)
bad magic 5a5a5a5a (should be cbe0cc60), wq bug, forcing oops.
kernel BUG at /usr/src/linux/include/asm/semaphore.h:185!
invalid operand: 0000
CPU: 1
EIP: 0010:[md_ioctl+2017/2076]
EFLAGS: 00010282
eax: 0000003a ebx: cbe0cc44 ecx: c03b2274 edx: c03b2268
esi: cbe0cc00 edi: ffffffea ebp: 400c0930 esp: cba79efc
ds: 0018 es: 0018 ss: 0018
Process raid0run (pid: 44, stackpage=cba79000)
Stack: c0339064 c0339120 000000b9 cbdfaae0 400c0930 cba43e80 00000000
cbe0cc00
bffffab0 00000000 00000000 00000004 00000001 c013eb79 cba74e40
cbdfaae0
cbdfaae0 cba74e40 00000000 cbe0b180 c0135c42 cba74e40 cbdfaae0
00010b40
Call Trace: [__mon_yday+15236/35340] [__mon_yday+15424/35340]
[blkdev_open+145/252] [dentry_open+190/348] [filp_open+82/92]
[blkdev_ioctl+40/52] [sys_ioctl+479/596]
[system_call+52/56]
Code: 0f 0b 83 c4 0c 89 d9 f0 ff 01 0f 8e 12 cc 12 00 eb 1e 68 ef
Regards,
Anton
-- Anton Altaparmakov Christ's College eMail: AntonA@bigfoot.com Cambridge CB2 3BU WWW: http://www-stu.christs.cam.ac.uk/~aia21/ United Kingdom ICQ: 8561279- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jun 26 2000 - 21:00:06 EST