[Bugme-janitors] [Bug 6965] Kernel doesn't re-sync usb-raid1 after running mdadm --add

bugme-daemon at bugzilla.kernel.org bugme-daemon at bugzilla.kernel.org
Wed Aug 9 10:58:44 PDT 2006


http://bugzilla.kernel.org/show_bug.cgi?id=6965





------- Additional Comments From kernel at blinkenlights.ch  2006-08-09 10:53 -------
Neil: btw:

using the internal bitmap wasn't such a good idea:

md0: bitmap file is out of date (0 < 20841588) -- forcing full recovery
md0: bitmap file is out of date, doing full recovery
md0: bitmap initialized from disk: read 10/10 pages, set 305174 bits, status: 0
created bitmap (150 pages) for device md0  <-- created bitmap
raid1: Disk failure on sda2, disabling device.  <-- failed a device
        Operation continuing on 1 devices
md: cannot remove active disk sda2 from md0 ... 
RAID1 conf printout: <-- removed it
 --- wd:1 rd:2
 disk 0, wo:0, o:1, dev:hda3
 disk 1, wo:1, o:0, dev:sda2
RAID1 conf printout:
 --- wd:1 rd:2
 disk 0, wo:0, o:1, dev:hda3
md: unbind<sda2>
md: export_rdev(sda2)
 
md: bind<sda2> <-- and re-added it .. -> boom!
RAID1 conf printout:
 --- wd:1 rd:2
 disk 0, wo:0, o:1, dev:hda3
 disk 1, wo:1, o:1, dev:sda2
md: syncing RAID array md0
md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec)
for reconstruction.
md: using 128k window, over a total of 19531136 blocks.
kernel BUG in sync_request at drivers/md/raid1.c:1748!
Oops: Exception in kernel mode, sig: 5 [#1]

Modules linked in: cls_fw sch_htb aes loop bsd_comp ppp_synctty ppp_async
ppp_generic slhc xt_length xt_MARK ipt_REJECT ipt_MASQUERADE xt_state ipt_LOG
iptable_mangle iptable_nat ip_nat iptable_filter
NIP: C01C6358 LR: C01C6328 CTR: 00000000
REGS: c64a7db0 TRAP: 0700   Not tainted  (2.6.18-rc3)
MSR: 00029032 <EE,ME,IR,DR>  CR: 24008024  XER: 00000000
TASK = dffdb220[18445] 'md0_resync' THREAD: c64a6000
GPR00: 00000000 C64A7E60 DFFDB220 00000001 00000000 C64A7E68 00000000 C01C5074 
GPR08: D54EA914 00000001 00000000 00000001 84008042 00000000 00000000 00000000 
GPR16: 00000000 00000000 00000000 00000001 00000000 02540B00 00001000 00000000 
GPR24: C1942000 00000000 00000001 C1936420 00000002 00000000 D54EA8E0 CE6466E0 
NIP [C01C6358] sync_request+0x3a0/0x59c
LR [C01C6328] sync_request+0x370/0x59c
Call Trace:
[C64A7E60] [C01C6328] sync_request+0x370/0x59c (unreliable)
[C64A7EB0] [C01CFD2C] md_do_sync+0x404/0x830
[C64A7F80] [C01CBFEC] md_thread+0x114/0x138
[C64A7FC0] [C003E618] kthread+0xc8/0x104
[C64A7FF0] [C0012A94] kernel_thread+0x44/0x60
Instruction dump:
2f830000 409e001c 801b0044 2f800000 409e0010 80180108 70050040 41820120 
80010008 21200007 39200000 7d294914 <0f090000> 5400482c 7f960000 409d0008 


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the Bugme-janitors mailing list