Another thought, I have several boxes running raid1's and raid5's under the same kernel. Does this bug affect only dom0 or only the way im nesting the raids? I will try a more recent dom0 kernel and see if that makes any difference in the meantime. - chris On Sun, Feb 21, 2010 at 4:17 AM, chris <tknchris@xxxxxxxxx> wrote: > Neil, > > The raid is being done in dom0, any idea how to set that from the > kernel cmdline? > > - chris > > On Sun, Feb 21, 2010 at 3:21 AM, Neil Brown <neilb@xxxxxxx> wrote: >> On Sun, 21 Feb 2010 19:16:40 +1100 >> Neil Brown <neilb@xxxxxxx> wrote: >> >>> On Sun, 21 Feb 2010 02:26:42 -0500 >>> chris <tknchris@xxxxxxxxx> wrote: >>> >>> > That is exactly what I didn't want to hear :( I am running >>> > 2.6.26-2-xen-amd64. Are you sure its a kernel problem and nothing to >>> > do with my chunk/block sizes? If this is a bug what versions are >>> > affected, I'll build a new domU kernel and see if I can get it working >>> > there. >>> > >>> > - chris >>> >>> I'm absolutely sure it is a kernel bug. >> >> though it just occurs to me that you might be able to work around it. >> If, in the guest, you set "max_sectors_kb" to "4" >> in /sys/block/whatever/queue, it might avoid the problem. >> >> NeilBrown >> >> >>> I have no idea what version might be affected. Probably all, but >>> as xen isn't fully in main line it isn't easy for me to explore. >>> >>> I suggest you contact the xen developers (or whoever you got xen from). >>> I'm happy to discuss the problem with someone who knows about xen block >>> device access, but I don't want to go hunting to find such a person. >>> >>> 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
