The raid code already does that kind of concurrency. Now the important clue
is probably
> More on this -- am also getting "..could not get a free page...". =
This indicates a memory allocation failed. That means its more likely someone
doesnt check a get_free_page/kmalloc return and continues blissfully into
oblivion mode.
Could be the driver fs or scsi layer. Are your other test setups producing
a "free page.." message too ? (ie the working ones)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/