Messages in this thread |  | | Date | Tue, 2 Oct 2001 07:19:49 +0200 | From | Jakob Østergaard <> | Subject | Re: RAID sync |
| |
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: > ... > 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 ?
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)
-- ................................................................ : jakob@unthought.net : 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}...............: - 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/
|  |