Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] Minor drbd 0.7 bugs
Date: Fri, 26 Jan 2007 16:24:08 +0100	[thread overview]
Message-ID: <20070126152408.GT4268@marowsky-bree.de> (raw)

Hi,

I played around with drbd0.7 and heartbeat on a lonely train ride
yesterday ;-)

- drbdadm disconnect seems to also demote a primary; I'd expect it to
  just disconnect it from the secondary?

- freeze_io doesn't seem to work. It freezes the Xen guest completely,
  not just the IO. My expectation would have been for it to freeze io,
  until either reconnected or explicitly told to disconnect and go to
  standalone mode?

- drbdadm primary does not bubble up errors from drbdsetup.

  ioctl(,SET_STATE,) failed: Permission denied
  Partner is already primary 
  Command '/sbin/drbd setup /dev/drbd0 primary' terminated with exit code 20
  drbdadm aborting

  Still, drbdadm returned with exit code 0.


Sincerely,
    Lars

-- 
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business	 -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge."


                 reply	other threads:[~2007-01-26 15:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20070126152408.GT4268@marowsky-bree.de \
    --to=lmb@suse.de \
    --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