This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: Debian, Xen and DRBD: Enabling true server redundancy

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: Debian, Xen and DRBD: Enabling true server redundancy
From: Helmut Wollmersdorfer <helmut.wollmersdorfer@xxxxxx>
Date: Wed, 15 Jun 2005 11:01:08 +0200
Delivery-date: Wed, 15 Jun 2005 09:05:13 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <31F19452BA8B2042A359D849B74B1BF005BCA2@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <31F19452BA8B2042A359D849B74B1BF005BCA2@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Debian Thunderbird 1.0.2 (X11/20050331)
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

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>