All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Berra <luca.berra@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: Question: array locking, possible?
Date: Thu, 9 Feb 2006 21:48:48 +0100	[thread overview]
Message-ID: <20060209204847.GA1387@percy.comedia.it> (raw)
In-Reply-To: <1C4766A743ADF74FAEDF2AAD0679BAA20767917E@cacexc03.americas.cpqcorp.net>

On Thu, Feb 09, 2006 at 10:28:58AM -0800, Stern, Rick (Serviceguard Linux) wrote:
>There is more interest, just not vocal.
>
>May want to look at LVM2 and its ability to use tagging to control enablement of VGs. This way it is not HW dependent.
>
I believe there is space in md1 superblock for a "cluster/exclusive"
flag, if not the name field could be used
what is missing is an interface between mdadm and cmcld so mdadm can ask
cmcld permission to activate an array with the "cluster/exclusive" flag
set.

L.

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

  reply	other threads:[~2006-02-09 20:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09 18:28 Question: array locking, possible? Stern, Rick (Serviceguard Linux)
2006-02-09 20:48 ` Luca Berra [this message]
2006-02-13 17:52   ` Chris Osicki
2006-02-13 21:53     ` Luca Berra
2006-02-13 22:54       ` Luca Berra
2006-02-13 17:12 ` Chris Osicki
  -- strict thread matches above, loose matches on Subject: below --
2006-02-13 17:21 Stern, Rick (Serviceguard Linux)
2006-02-13 17:58 ` Chris Osicki
2006-02-07 17:55 Chris Osicki
2006-02-07 18:16 ` Mike Hardy
2006-02-08 10:49   ` Chris Osicki
2006-02-07 19:26 ` Paul Clements
2006-02-08 10:55   ` Chris Osicki
2006-02-08 20:45     ` Jure Pečar
2006-02-09 10:25       ` Chris Osicki
2006-02-10  0:00         ` Neil Brown
2006-02-10 17:17       ` Paul Clements

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=20060209204847.GA1387@percy.comedia.it \
    --to=luca.berra@comedia.it \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.