From: Robert Heinzmann <Robert.Heinzmann@gmx.net>
To: linux-raid@vger.kernel.org
Subject: Raid1 "synchronous" mirror question
Date: Tue, 06 Dec 2005 10:46:55 +0100 [thread overview]
Message-ID: <43955E0F.6090704@gmx.net> (raw)
Hello,
I'm currently trying to understand the "flow" of the I/O in Linux raid1
devices in regard to superblock updates and resynces on machine crashes.
I looked at the source (2.6 kernel) and made some guesses about the
working of the raid1 kernel module. The problem is that I'm not an
kernel expert so I try to point out the basic algotithms and it would be
great if some expert could give ma a yes/no answer :)
1) As soon as the first write is made, the superblock is updated and
mddev->in_sync is set to 0
2) There is a machanism (can you tell me which part of the kernel does
this ?) that looks if all write requests have been written to both disks
and if no write requests are queued anymore, the superblock is updated
with the information mddev->in_sync=1
The question is, whats the maximal time that data can be "out of sync"
on both mirrors making the mirror an NON-synchronous mirror ?
Is there a way to make the mirror a "real" synchronous mirror ?
Regards,
Robert Heinzmann
next reply other threads:[~2005-12-06 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 9:46 Robert Heinzmann [this message]
2005-12-07 0:01 ` Raid1 "synchronous" mirror question Neil Brown
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=43955E0F.6090704@gmx.net \
--to=robert.heinzmann@gmx.net \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).