From: Frank van Maarseveen <frankvm@frankvm.com>
To: linux-raid@vger.kernel.org
Subject: raid1 resync data direction defined?
Date: Fri, 27 Jul 2007 15:07:13 +0200 [thread overview]
Message-ID: <20070727130713.GA12058@janus> (raw)
I'm experimenting with a "live" migration of /dev/sda1 using mdadm -B
and network block device as in:
mdadm -B -ayes -n2 -l1 /dev/md1 /dev/sda1 \
--write-mostly -b /tmp/bitm$$ --write-behind /dev/nbd1
/dev/sda1 is to be migrated. During the migration the local system
mounts from /dev/md1 instead. Stracing shows that data flows to the
remote side. But when I do
echo repair >/sys/block/md1/md/sync_action
then the data flows in the other direction: the local disk is written
using data read from the remote side.
If that would happen in the first command then it would destroy all
data instead of migrating it so I wonder if this behavior is defined:
Do mdadm --build and mdadm --create always use the first component device
on the command-line as the source for raid1 resync?
--
Frank
next reply other threads:[~2007-07-27 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 13:07 Frank van Maarseveen [this message]
2007-07-30 8:09 ` raid1 resync data direction defined? Luca Berra
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=20070727130713.GA12058@janus \
--to=frankvm@frankvm.com \
--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).