On 15 Jan 2007, Bill Davidsen told this:
Nix wrote:
Number Major Minor RaidDevice State
0 860 active sync /dev/sda6
1 8 221 active sync /dev/sdb6
3 2252 active sync /dev/hdc5
On 14 Jan 2007, Neil Brown told this:
A quick look suggests that the following patch might make a
difference, but there is more to it than that. I think there are
subtle differences due to the use of version-1 superblocks. That
might be just another one-line change, but I want to make sure
On 13 Jan 2007, [EMAIL PROTECTED] uttered the following:
mdadm-2.6 bug, I fear. I haven't tracked it down yet but will look
shortly: I can't afford to not run mdadm --monitor... odd, that
code hasn't changed during 2.6 development.
Whoo! Compile Monitor.c without optimization and the problem
On Sunday January 14, [EMAIL PROTECTED] wrote:
On 13 Jan 2007, [EMAIL PROTECTED] uttered the following:
mdadm-2.6 bug, I fear. I haven't tracked it down yet but will look
shortly: I can't afford to not run mdadm --monitor... odd, that
code hasn't changed during 2.6 development.
Whoo!
On 12 Jan 2007, Ernst Herzberg told this:
Then every about 60 sec 4 times
event=SpareActive
mddev=/dev/md3
I see exactly this on both my RAID-5 arrays, neither of which have any
spare device --- nor have any active devices transitioned to spare
(which is what that event is actually supposed
On Fri, 12 Jan 2007, Neil Brown might have said:
On Thursday January 11, [EMAIL PROTECTED] wrote:
Can someone tell me what this means please? I just received this in
an email from one of my servers:
A FailSpare event had been detected on md device /dev/md2.
It could
On 13 Jan 2007, [EMAIL PROTECTED] spake thusly:
On 12 Jan 2007, Ernst Herzberg told this:
Then every about 60 sec 4 times
event=SpareActive
mddev=/dev/md3
I see exactly this on both my RAID-5 arrays, neither of which have any
spare device --- nor have any active devices transitioned to
On 13 Jan 2007, [EMAIL PROTECTED] uttered the following:
On 12 Jan 2007, Ernst Herzberg told this:
Then every about 60 sec 4 times
event=SpareActive
mddev=/dev/md3
I see exactly this on both my RAID-5 arrays, neither of which have any
spare device --- nor have any active devices
On Thursday 11 January 2007 23:23, Neil Brown wrote:
On Thursday January 11, [EMAIL PROTECTED] wrote:
Can someone tell me what this means please? I just received this in
an email from one of my servers:
Same problem here, on different machines. But only with mdadm 2.6, with
mdadm
Can someone tell me what this means please? I just received this in
an email from one of my servers:
From: mdadm monitoring [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: FailSpare event on /dev/md2:$HOST.$DOMAIN.com
This is an automatically generated mail message from mdadm
running on $HOST
On Thursday January 11, [EMAIL PROTECTED] wrote:
Can someone tell me what this means please? I just received this in
an email from one of my servers:
A FailSpare event had been detected on md device /dev/md2.
It could be related to component device /dev/sde2.
It means that mdadm
On Fri, 12 Jan 2007, Neil Brown might have said:
On Thursday January 11, [EMAIL PROTECTED] wrote:
Can someone tell me what this means please? I just received this in
an email from one of my servers:
A FailSpare event had been detected on md device /dev/md2.
It could
On Thursday January 11, [EMAIL PROTECTED] wrote:
So I'm ok for the moment? Yes, I need to find the error and fix everything
back to the (S) state.
Yes, OK for the moment.
The messages in $HOST:/var/log/messages for the time of the email are:
Jan 11 16:04:25 elo kernel: sd 2:0:4:0: SCSI
google BadBlockHowto
Any just google it response sounds glib, but this is actually how to
do it :-)
If you're new to md and mdadm, don't forget to actually remove the drive
from the array before you start working on it with 'dd'
-Mike
Mike wrote:
On Fri, 12 Jan 2007, Neil Brown might have
2007/1/12, Mike [EMAIL PROTECTED]:
# 1 Background long Completed, segment failed -3943
This should still be in warranty. Try to get a replacement.
Best
Martin
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More
15 matches
Mail list logo
