Tuesday, October 02, 2001, 9:19:49 AM, you wrote:
JŲ> On Mon, Oct 01, 2001 at 06:27:53PM +0400, Oleg A. Yurlov wrote:
>>
>> Privet :-)
>>
>> Kernel 2.4.6.SuSE-4GB-SMP, 2 CPU, 2Gb RAM, 4 HDD SCSI, M/B Intel L440GX.
>> Messages from dmesg:
>>
JŲ> ...
>> md: sdc2 [events: 0000001e](write) sdc2's sb offset: 15815872
>> md: considering sdb2 ...
>> md: adding sdb2 ...
>> md: adding sda2 ...
>> md: created md0
>> md: bind<sda2,1>
>> md: bind<sdb2,2>
>> md: running: <sdb2><sda2>
>> md: now!
>> md: sdb2's event counter: 0000001c
>> md: sda2's event counter: 0000001d
>> md: superblock update time inconsistency -- using the most recent one
>> md: freshest: sda2
>> md0: max total readahead window set to 508k
>> md0: 1 data-disks, max readahead per data-disk: 508k
>> raid1: device sdb2 operational as mirror 1
>> raid1: device sda2 operational as mirror 0
>> raid1: raid set md0 active with 2 out of 2 mirrors
>> md: updating md0 RAID superblock on device
>> md: sdb2 [events: 0000001e](write) sdb2's sb offset: 15815872
>> md: sda2 [events: 0000001e](write) sda2's sb offset: 15815872
>> md: ... autorun DONE.
>>
>> Why RAID do not start synchronization ? It is normal ?
JŲ> Doesn't it ?
Really.
JŲ> Try "cat /proc/mdstat"
JŲ> Synchronization is a background operation - your array is functional
JŲ> immediately.
No, synchronization not started, /proc/mdstat say that RAID is Ok
([UU]). /proc/mdstat checked immediately after booting.
JŲ> (this behaviour was changed from the really really old RAID code in unpatched
JŲ> 2.2 to standard 2.4)
Neil already has given some explanations...
-- 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/