On Saturday February 4, [EMAIL PROTECTED] wrote:
> > Ahh, i almost forget!
> > The mdadm is sometimes drop "cannot allocate memory" and next try
> "segfault"
> > when i try -G --bitmap=internal on 2TB arrays!
> > And after segfault, the full raid is stops...
> >
> > Cheers,
> > Janos
>
> I think i
> Ahh, i almost forget!
> The mdadm is sometimes drop "cannot allocate memory" and next try
"segfault"
> when i try -G --bitmap=internal on 2TB arrays!
> And after segfault, the full raid is stops...
>
> Cheers,
> Janos
I think i found the bug, its me. :-)
Today it happens again, and i see, i hav
- Original Message -
From: "Neil Brown" <[EMAIL PROTECTED]>
To: "JaniD++" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, February 03, 2006 1:23 AM
Subject: Re: raid 4, and bitmap.
> On Friday February 3, [EMAIL PROTECTED] wrote:
>
On Friday February 3, [EMAIL PROTECTED] wrote:
> >
> > If it is an internal bitmap it should work.
> > Are there any kernel messages during boot that might be interesting?
>
> Sorry, i did not log this, and i dont want to restart the sync and system
> for this.
> Anyway, i add back the bitmap,
- Original Message -
From: "JaniD++" <[EMAIL PROTECTED]>
To: "Neil Brown" <[EMAIL PROTECTED]>
Sent: Friday, February 03, 2006 1:20 AM
Subject: Re: raid 4, and bitmap.
>
> - Original Message -
> From: "Neil Brown" <[EMAI
- Original Message -
From: "Neil Brown" <[EMAIL PROTECTED]>
To: "JaniD++" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, February 03, 2006 1:09 AM
Subject: Re: raid 4, and bitmap.
> On Friday February 3, [EMAIL PROTECTED] wrote:
> > Hello, list, Neil,
&
On Friday February 3, [EMAIL PROTECTED] wrote:
> Hello, list, Neil,
>
> I try to add bitmaps to raid4, and mdadm is done this fine.
> In the /proc/mdstat shows this, and it is really works well.
>
> But on reboot, the kernel drops the bitmap(, and resync the entire array if
> it is unclean). :(
>
