From: "Oleg A. Yurlov" <kris@spylog.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org, admin@spylog.com
Subject: Re[2]: RAID sync
Date: Tue, 9 Oct 2001 23:37:19 +0400 [thread overview]
Message-ID: <8371332758.20011009233719@spylog.com> (raw)
In-Reply-To: <15298.13864.971940.46509@notabene.cse.unsw.edu.au>
In-Reply-To: <1101445461994.20011001182753@spylog.com> <15298.13864.971940.46509@notabene.cse.unsw.edu.au>
Hi, Neil,
Tuesday, October 09, 2001, 3:26:32 AM, you wrote:
>> Kernel 2.4.6.SuSE-4GB-SMP, 2 CPU, 2Gb RAM, 4 HDD SCSI, M/B Intel L440GX.
>> Messages from dmesg:
NB> snip
>> md: now!
>> md: sdb2's event counter: 0000001c
>> md: sda2's event counter: 0000001d
NB> snip
>> Why RAID do not start synchronization ? It is normal ?
NB> Yes.
NB> A difference of 1 in the event counters isn't considered enough to
NB> treat on of them as old, and presumably the newest one (sda2) was
NB> marked clean.
NB> This could happen if the array was shut down cleanly, the new super
NB> block (with the dirty bit cleared) was written to sda2, but the new
NB> superblock was NOT written to sdb2 for some reason. In this situation
NB> there is no need to resync the array.
NB> Could this be what happened in your case?
Server is slow die (error in VM, server lost procfs) and rebooted by
'reboot -f'... I don't know what happen with RAID in this case.
NB> NeilBrown
--
Oleg A. Yurlov aka Kris Werewolf, SysAdmin OAY100-RIPN
mailto:kris@spylog.com +7 095 332-03-88
prev parent reply other threads:[~2001-10-09 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 14:27 Oleg A. Yurlov
2001-10-02 5:19 ` Jakob Østergaard
2001-10-08 23:26 ` Neil Brown
2001-10-09 19:32 ` Re[2]: " Oleg A. Yurlov
2001-10-10 5:58 ` Jakob Østergaard
2001-10-09 19:37 ` Oleg A. Yurlov [this message]
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=8371332758.20011009233719@spylog.com \
--to=kris@spylog.com \
--cc=admin@spylog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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
Powered by JetHome