Skip to contentSkip to conversation

RAID sync

DISCUSSION Oleg A. Yurlov 2 participants 4 messages Oct 1, 2001 – Oct 10, 2001

lore
Share & tools
lore
#0 lore raw
        Привет :-)

        Kernel 2.4.6.SuSE-4GB-SMP, 2 CPU, 2Gb RAM, 4 HDD SCSI, M/B Intel L440GX.

Messages from dmesg:

(scsi0:0:3:0) Synchronous at 80.0 Mbyte/sec, offset 63. SCSI device sdd: 35843670 512-byte hdwr sectors (18352 MB)
sdd: sdd1 sdd2
md: raid1 personality registered
md: raid5 personality registered
raid5: measuring checksumming speed

   8regs     :  1321.600 MB/sec
   32regs    :   978.400 MB/sec
   pIII_sse  :  1632.400 MB/sec
   pII_mmx   :  1790.000 MB/sec
   p5_mmx    :  1885.200 MB/sec

raid5: using function: pIII_sse (1632.400 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
(read) sda2's sb offset: 15815872 [events: 0000001d] (read) sdb2's sb offset: 15815872 [events: 0000001c] (read) sdc2's sb offset: 15815872 [events: 0000001d] (read) sdd2's sb offset: 15815872 [events: 0000001d]

md: autorun ...
md: considering sdd2 ...
md:  adding sdd2 ...
md:  adding sdc2 ...
md: created md1
md: bind<sdc2,1>
md: bind<sdd2,2>
md: running: <sdd2><sdc2>
md: now!
md: sdd2's event counter: 0000001d
md: sdc2's event counter: 0000001d
md1: max total readahead window set to 508k
md1: 1 data-disks, max readahead per data-disk: 508k
raid1: device sdd2 operational as mirror 1
raid1: device sdc2 operational as mirror 0
raid1: raid set md1 active with 2 out of 2 mirrors
md: updating md1 RAID superblock on device
md: sdd2 [events: 0000001e](write) sdd2's sb offset: 15815872
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 ?

--
Oleg A. Yurlov aka Kris Werewolf, SysAdmin OAY100-RIPN
mailto:[email protected] +7 095 332-03-88

#1 lore raw
Quoted 6 lines · Oleg A. Yurlov
        Privet :-)

        Kernel 2.4.6.SuSE-4GB-SMP, 2 CPU, 2Gb RAM, 4 HDD SCSI, M/B Intel L440GX.

Messages from dmesg:

...

Quoted 23 lines
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.
Quoted 1 line

Why RAID do not start synchronization ? It is normal ?

Doesn't it ?

Try "cat /proc/mdstat"

Synchronization is a background operation - your array is functional immediately.

(this behaviour was changed from the really really old RAID code in unpatched
2.2 to standard 2.4)

Signature · 6 lines
................................................................
:   [email protected]   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:
#2 lore raw

Hi, Jakob and all,

Tuesday, October 02, 2001, 9:19:49 AM, you wrote:

Quoted 6 lines · Oleg A. Yurlov
Quoted 6 lines
        Privet :-)

        Kernel 2.4.6.SuSE-4GB-SMP, 2 CPU, 2Gb RAM, 4 HDD SCSI, M/B Intel L440GX.

Messages from dmesg:

JØ> ...

Quoted 23 lines
Quoted 23 lines
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.
Quoted 1 line
Quoted 1 line

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:[email protected] +7 095 332-03-88

#3 lore raw
In reply to Oleg A. Yurlov
Quoted 2 lines · Oleg A. Yurlov

Hi, Jakob and all,

...

Quoted 11 lines

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...

I was too quick, and as far as I can see, Neil gave the correct explanation.

Hey, maybe I was wrong, but I was *faster* ;)

Signature · 6 lines
................................................................
:   [email protected]   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............: