Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Wed, Jun 14, 2006 at 07:34:56PM +0530, Milind Dumbare wrote:
> Hi All,
>
> I have installed DRBD on my machines ( One is "Dhruva" Fedora Core 5
> i386 and other is "Tucker" Ubuntu 5.0 x86_64 )
> I patched Linux-2.6.15 with drbd-0.7.19 patches and installed the
> kernel. DRBD is built-in in kernel. ( Not Module)
>
> following is my /etc/drbd.conf
> ===============================
> resource RES1 {
> protocol C;
> incon-degr-cmd "wall Beware";
>
> on dhruva {
> device /dev/drbd0;
> disk /dev/hda8;
> address 192.168.1.18:7789;
> meta-disk internal;
> }
> on tucker {
> device /dev/drbd0;
> disk /dev/sda5;
> address 192.168.1.5:7789;
> meta-disk internal;
> }
> }
> =================================
>
> So as far as I understood "dhruva" is primary and "tucker" is secondary,
> am I right?
No. The one that you define as primary, in the command line, gets to be
primary. There is no default.
> So when I will write any data to /dev/hda8 of dhruva it will be
> replicated to /dev/sda5, isn't it?
No. You have to use /dev/drbd0, not the backend devices.
> I have /dev/hda8 of Dhruva of 10GB size and /dev/sda5 of Tucker of 21GB
> size, so it wont cause problem, which is discussed in FAQs, right?
Yes, you'll be limited to ~ 10GB, though.
> Please help me out with abouve three questions.
Please read the documentation...
--
lfr
0/0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20060614/65f7f23e/attachment.pgp>