On 04/19/2011 06:51 PM, NeilBrown wrote:
On Tue, 19 Apr 2011 12:03:27 -0400 Iordan Iordanov<iordan@xxxxxxxxxxxxxxx>
[...]
If there was such a deadlock, it would be a serious bug. I don't believe
such a bug exists (but hey - I keep finding bugs in this code, when I'm not
busy writing new bugs, so I guess it could crash you machine and kill your
cat).
I ran into this a few years ago (early 2.6 series, maybe 2.6.15 or so).
Some sort of race condition. Required a reset to get the machines
attention. Haven't tried since. Since we do lots of MD raid, I
generally either put the swap on hardware RAID, or stripe it and
sometimes hope for the best. The latter doesn't always work. When a
drive goes pear shaped, and takes down pages with it, your machine will
crash, and pretty hard at that.
We'll definitely try the swap atop MD RAID going forward. I like the
idea of a RAID10 for it.
It would be nice to have a discussion among people who have experience
with all of this.
Definitely put swap on RAID1 if you have RAID1 at all.
My personal preference with RAID1 to to have a single RAID1 (probably
--metadata=1.0) across the whole devices, and partition that for root, swap,
home.
This gets to my question, since we haven't tried this yet ... can we do
whole device MD RAIDs, and boot from them? Is there anything special we
need to do in their construction (use --auto=mdp or similar)? We'd
really prefer to go this route rather than building multiple smaller
RAIDs. We can manage the latter, but the former is far easier/cleaner
to handle rebuilds with.
Regards,
Joe
--
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics, Inc.
email: landman@xxxxxxxxxxxxxxxxxxxxxxx
web : http://scalableinformatics.com
http://scalableinformatics.com/sicluster
phone: +1 734 786 8423 x121
fax : +1 866 888 3112
cell : +1 734 612 4615
--
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
