On Wednesday December 6, [EMAIL PROTECTED] wrote:
Neil Brown wrote:
Could you try this patch and see how it goes?
Same result!
Ok... must be something else... I tried again to reproduce it, and
this time I succeeded.
The problem happens when you try to access the last 128k of a raid1
Neil Brown wrote:
On Tuesday November 28, [EMAIL PROTECTED] wrote:
Hi Neil!
I did a raidsetfaulty - raidhotremove - raidhotadd sequence and hit an Oops.
I refer to a posting of you about raid5 where you suggested this to a guy
and so I thought this should work, but I always get an
Friedrich Lobenstock wrote:
My guess is that hdc1 was the "current drive" (-last_used) when you
did that setfaulty, and still when you did the raidhotadd, and trying
to rebuild from that drive causes the Oopps.
If I am right, then you should get this result about half the time
that
