From: NeilBrown <neilb@suse.de>
To: Tejas Rao <raot@bnl.gov>, Scott Sinno <scott.sinno@nasa.gov>,
linux-raid@vger.kernel.org
Cc: "Knister,
Aaron S. (GSFC-606.2)[COMPUTER SCIENCE CORP]"
<aaron.s.knister@nasa.gov>
Subject: Re: clustered MD - beyond RAID1
Date: Tue, 22 Dec 2015 07:47:12 +1100 [thread overview]
Message-ID: <87bn9j4jhr.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <567850C4.30108@bnl.gov>
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
On Tue, Dec 22 2015, Tejas Rao wrote:
> What if the application is doing the locking and making sure that only 1
> node writes to a md device at a time? Will this work? How are rebuilds
> handled? This would be helpful with distributed filesystems like
> GPFS/lustre etc.
>
You would also need to make sure that the filesystem only wrote from a
single node at a time (or access the block device directly). I doubt
GPFS/lustre make any promise like that, but I'm happy to be educated.
rebuilds are handled by using a cluster-wide lock to block all writes to
a range of addresses while those stripes are repaired.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2015-12-21 20:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 15:29 clustered MD - beyond RAID1 Scott Sinno
2015-12-20 23:25 ` NeilBrown
2015-12-21 19:19 ` Tejas Rao
2015-12-21 20:47 ` NeilBrown [this message]
2015-12-21 21:27 ` Tejas Rao
2015-12-21 22:03 ` NeilBrown
2015-12-21 22:29 ` Adam Goryachev
2015-12-21 23:09 ` NeilBrown
2015-12-22 1:36 ` Tejas Rao
2015-12-22 2:29 ` Alireza Haghdoost
2015-12-22 4:13 ` NeilBrown
[not found] ` <CAB9NSeXhoHd3_BDRrWAsBrW0Dj2=NucyUFt8pSP0zB5K=RkUOg@mail.gmail.com>
2016-12-05 1:46 ` Aaron Knister
[not found] ` <5678A2B9.6070008@bnl.gov>
2015-12-22 1:50 ` Aaron Knister
2015-12-22 2:33 ` Tejas Rao
[not found] ` <5678B693.40907-IGkKxAqZmp0@public.gmane.org>
2015-12-25 8:47 ` roger zhou
-- strict thread matches above, loose matches on Subject: below --
2016-12-02 18:12 Robert Woodworth
2016-12-02 20:02 ` Shaohua Li
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=87bn9j4jhr.fsf@notabene.neil.brown.name \
--to=neilb@suse.de \
--cc=aaron.s.knister@nasa.gov \
--cc=linux-raid@vger.kernel.org \
--cc=raot@bnl.gov \
--cc=scott.sinno@nasa.gov \
/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).