Re: Re: fr1-2.16 patch for 2.6.10 kernel

denis bonnenfant <[email protected]>
Newsgroups gmane.linux.enbd.general
Message-ID <[email protected]>
Peter T. Breuer a écrit :
> 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.
Ok, I'm going to do that
> 
> 
> 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 ...

I tried with 2.6.10 too, but stop investigating, as drivers for my hw are broken...

>    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?
No, the problem occurs even if you don't wait the total reconstuction for fault/add.
But do you have the "bitmap f7cbb740 already active!" message when failing disk ?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.