All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helmut Wollmersdorfer <helmut.wollmersdorfer@gmx.at>
To: xen-devel@lists.xensource.com
Subject: Re: Debian, Xen and DRBD: Enabling true server redundancy
Date: Wed, 15 Jun 2005 11:01:08 +0200	[thread overview]
Message-ID: <d8oqf2$sop$1@sea.gmane.org> (raw)
In-Reply-To: <31F19452BA8B2042A359D849B74B1BF005BCA2@aklexch01.nsp.local>

Tom Hibbert wrote:

> # modprobe drbd

> Note that drbd can only be configured as a module (for reasons
> unfathomable to me).

Some people compile it into the kernel, which should work.
If not with a XENized one, maybe somebody on the drdb-lists has a solution.

> The builtin drbddisk resource handler had some problems, so I modified
> it slightly.

If you report this to the developers of DRBD, this would be fine.

> Please give me some feedback on this documentation style. 

First, great thanks for your doc.

Some people do not like this 'on my $distro I did' style.

IMHO it is very valuable for others, and has a high cost/benefit ratio.
Ideally an author of such a Mini-HOWTO avoids the common mistakes, which 
  potentially lead to confusion:
- don't use 'now', 'current version', use explicite dates like '15th Jun
   2005', and full version numbers like 'kernel-source-2.6.8-15 from
   Debian Sarge'
- try to list all preconditions, which are different from a plain
   default installation
- the history listing of the console commands should be complete,
   i.e. contain even such unimportant things like 'cd ..'. Sometimes it
   is better to write 'compile the kernel with patches and install it',
   than a list of an _incomplete_ history.
- use full paths of files and directories
- use copies of the command line, where anybody can see the current
   host, current user, current directory, e.g.
   'helmut@node1:~$ cat /proc/drdb'
   Especially on clusters the node/host is important.
- describe diagnostics like you did with e.g. 'cat /proc/drbd'

BTW: As I understand, you mount a DRBD-device for the whole '/' of the 
guest. I will try the similar idea with www.linux-vserver.org instead of 
XEN.

Helmut Wollmersdorfer

  parent reply	other threads:[~2005-06-15  9:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14 22:16 Debian, Xen and DRBD: Enabling true server redundancy Tom Hibbert
2005-06-15  7:04 ` Michael Paesold
2005-06-15  9:01 ` Helmut Wollmersdorfer [this message]
2005-06-15 10:50 ` Nils Toedtmann

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='d8oqf2$sop$1@sea.gmane.org' \
    --to=helmut.wollmersdorfer@gmx.at \
    --cc=xen-devel@lists.xensource.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.