Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Cristian Zamfir <zamf@dcs.gla.ac.uk>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] lock for reading device state
Date: Wed, 06 Dec 2006 17:22:43 +0000	[thread overview]
Message-ID: <4576FC63.704@dcs.gla.ac.uk> (raw)



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. Is there a way to obtain a lock while reading and 
processing this information and prevent other writes to the primary 
device? I need to be able to prevent writes while reading the state of 
the device from a script external to drbd.

In case there is no existing solution, can you please give me a few tips 
on how to start developing such a locking mechanism?

Thank you very much.


Cristian

             reply	other threads:[~2006-12-06 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 17:22 Cristian Zamfir [this message]
2006-12-07 13:09 ` [Drbd-dev] lock for reading device state Lars Ellenberg
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=4576FC63.704@dcs.gla.ac.uk \
    --to=zamf@dcs.gla.ac.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox