lkml.org 
[lkml]   [2001]   [Oct]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: RAID sync
On Monday October 1, kris@spylog.com wrote:
>
> Kernel 2.4.6.SuSE-4GB-SMP, 2 CPU, 2Gb RAM, 4 HDD SCSI, M/B Intel L440GX.
> Messages from dmesg:
snip
> md: now!
> md: sdb2's event counter: 0000001c
> md: sda2's event counter: 0000001d
snip
>
> Why RAID do not start synchronization ? It is normal ?

Yes.
A difference of 1 in the event counters isn't considered enough to
treat on of them as old, and presumably the newest one (sda2) was
marked clean.
This could happen if the array was shut down cleanly, the new super
block (with the dirty bit cleared) was written to sda2, but the new
superblock was NOT written to sdb2 for some reason. In this situation
there is no need to resync the array.

Could this be what happened in your case?

NeilBrown


>
> --
> Oleg A. Yurlov aka Kris Werewolf, SysAdmin OAY100-RIPN
> mailto:kris@spylog.com +7 095 332-03-88
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:05    [W:0.086 / U:1.444 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site