public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Oleg A. Yurlov" <kris@spylog.com>
To: "Jakob Østergaard" <jakob@unthought.net>
Cc: linux-kernel@vger.kernel.org, admin@spylog.com
Subject: Re[2]: RAID sync
Date: Tue, 9 Oct 2001 23:32:40 +0400	[thread overview]
Message-ID: <129371054468.20011009233240@spylog.com> (raw)
In-Reply-To: <20011002071949.B5302@unthought.net>
In-Reply-To: <1101445461994.20011001182753@spylog.com> <20011002071949.B5302@unthought.net>


        Hi, Jakob and all,

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


  reply	other threads:[~2001-10-09 19:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-01 14:27 RAID sync Oleg A. Yurlov
2001-10-02  5:19 ` Jakob Østergaard
2001-10-09 19:32   ` Oleg A. Yurlov [this message]
2001-10-10  5:58     ` Re[2]: " Jakob Østergaard
2001-10-08 23:26 ` Neil Brown
2001-10-09 19:37   ` Re[2]: " Oleg A. Yurlov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=129371054468.20011009233240@spylog.com \
    --to=kris@spylog.com \
    --cc=admin@spylog.com \
    --cc=jakob@unthought.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox