From: Lars Ellenberg <Lars.Ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] lock for reading device state
Date: Thu, 7 Dec 2006 14:09:20 +0100 [thread overview]
Message-ID: <20061207130920.GD7521@soda.linbit> (raw)
In-Reply-To: <4576FC63.704@dcs.gla.ac.uk>
/ 2006-12-06 17:22:43 +0000
\ Cristian Zamfir:
>
>
> Hi,
>
> I am using drbd to implement xen block device migration. Right now I
> am parsing /proc/drbd to find out if the drives are synchronized and I
> can migrate them.
you talk about drbd state "Connected, Consistent",
or what exactly are you parsing?
> Is there a way to obtain a lock while reading and processing this
> information and prevent other writes to the primary device?
no. why?
> I need to be able to prevent writes while reading the state of
> the device from a script external to drbd.
does not make sense to me yet?
> In case there is no existing solution, can you please give me a few
> tips on how to start developing such a locking mechanism?
please give more details about your assumptions and reasoning,
maybe its just that you have wrong expectations?
could also be that I'm just mentally block right now...
:)
--
: Lars Ellenberg Tel +43-1-8178292-55 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe http://www.linbit.com :
next prev parent reply other threads:[~2006-12-07 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 17:22 [Drbd-dev] lock for reading device state Cristian Zamfir
2006-12-07 13:09 ` Lars Ellenberg [this message]
2006-12-07 13:52 ` Cristian Zamfir
2006-12-07 15:56 ` Lars Ellenberg
2006-12-07 20:25 ` Cristian Zamfir
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=20061207130920.GD7521@soda.linbit \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.linbit.com \
/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.