From: Neil Matai <neil@matai.kiwi.nz>
To: linux-raid@vger.kernel.org
Subject: Re: Simultaneous assembly on multiple hosts
Date: Sat, 4 May 2013 15:22:26 +1200 [thread overview]
Message-ID: <20130504032226.GE31411@chc-5.metaname.net> (raw)
In-Reply-To: <CALFpzo6CUZSeAcNK1A=8HdyjaGnKiN4Mtt01u_w=3p7WG-wY2A@mail.gmail.com>
On Fri, May 03, 2013 at 08:25:59PM -0600, Marcus Sorensen wrote:
> > Is it dangerous have an array assembled on two hosts at the same time?
> > Say I have servers A and B exporting devices a and b via ATA over
> > Ethernet or similar to hosts C and D. If a and b are components of an
> > array then both C and D automatically assemble the array as soon as
> > the components a and b are exported but is this safe (on the proviso
> > that only one of C or D is ever writing to the array at any time and
> > that there is no write-behind caching above the array device)?
> Yes, it is dangerous. There are some limited situations where it may work,
> without a bitmap and some cluster aware application in control of what
> blocks are written, but you can't for example mount it ext4 and write to
> only one side at a time. That's why people use drbd.
Sorry. I should have said what it was for. I realise that mounting a
typical file system twice would be dangerous (also with drdb). The
intention would have been to live migrate guest systems between C and
D so the file system remains mounted (once) inside the guest system
but nowhere else. Would it work in this scenario without a bitmap or
would this scenario also lead to data loss? Would it make any
difference if 0.9 metadata were use to create the array?
Many thanks,
- neil
next prev parent reply other threads:[~2013-05-04 3:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 2:01 Simultaneous assembly on multiple hosts Neil Matai
[not found] ` <CALFpzo6CUZSeAcNK1A=8HdyjaGnKiN4Mtt01u_w=3p7WG-wY2A@mail.gmail.com>
2013-05-04 3:22 ` Neil Matai [this message]
2013-05-06 6:32 ` NeilBrown
2013-05-06 9:05 ` Sebastian Riemer
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=20130504032226.GE31411@chc-5.metaname.net \
--to=neil@matai.kiwi.nz \
--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