Re: fr1-2.16 patch for 2.6.10 kernel
[email protected] (Peter T. Breuer)
| Newsgroups | gmane.linux.enbd.general |
|---|---|
| Message-ID | <[email protected]> |
In article <[email protected]> you wrote: > Anyway, the problem must be in hot_add_disk(), so if you could sprinkle > printk's through there (at the start, for instance!) that would be > helpful. I also wonder if the problem is particular to 2.6.8.1, because on 2.6.3 (where I am!) I can fault and repair the array seemingly without problems as many times as I like ... 640 19:44 sudo mdadm -C -l 1 -n 2 -x 0 /dev/md0 /dev/loop{0,1} 641 19:44 cat /proc/mdstat 642 19:44 cat /proc/mdstat 643 19:44 sync 644 19:46 sudo raidsetfaulty /dev/md0 /dev/loop1 645 19:46 cat /proc/mdstat 646 19:46 sudo raidhotadd /dev/md0 /dev/loop1 647 19:46 sync 648 19:46 cat /proc/mdstat 649 19:46 dmesg 650 19:48 sudo raidsetfaulty /dev/md0 /dev/loop1 651 19:48 cat /proc/mdstat 652 19:48 sudo raidhotadd /dev/md0 /dev/loop1 653 19:48 sync 654 19:48 cat /proc/mdstat 655 19:48 sudo raidsetfaulty /dev/md0 /dev/loop1 656 19:48 cat /proc/mdstat 657 19:48 sudo raidhotadd /dev/md0 /dev/loop1 658 19:48 sudo raidsetfaulty /dev/md0 /dev/loop1 659 19:48 cat /proc/mdstat 660 19:48 sudo raidhotadd /dev/md0 /dev/loop1 661 19:48 sync and no kernel oops. Am I supposed to dirty the array to get the problem? Peter