On Sat, June 27, 2009 3:16 pm, satha wrote: > Hi All, > > Iam using 2.6.27 kernel. Connected 8 disks using Silicon Image and > Marvell > Rocket RAID PCIe express cards. > > Can any one help me in debugging the following problem: > > There is a kernel bug detected in __get_priority_stripe() > BUG_ON(atomic_read(&sh->count) != 1) while testing RAID5, > writing morethan 20GB data using dd, several times. > > Is Iam missing any configurations, can anyone briefly explain what exactly > this function doing. The function chooses the next stripe that needs to be 'handled'. It either takes one from 'handle list' - which are completely ready to be handed, or from 'hold list' which are reluctantly ready to be handled... but they would be happy to wait a bit longer in case some more blocks were added to it. Stripes are only every added to handle_list or delay_list when their ->count is zero. They only get on to hold_list straight off delay_list, and they only ever have their ->count increment when either: it is already non-zero or the stripe has just been removed from any list. So that BUG cannot possibly happen :-) Is it repeatable at all? If there any chance of bad memory? NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
