Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I believe I have correctly set up drbd on a Debian(sarge) box.
Can I just test it on one box without having a secondary server yet?
That is, I want to be able to mount the drbd block device and write
to it.
So, here is what I have so far.
My drbd.conf reads:
> resource r0 {
> protocol c;
> on Pacifica {
> device /dev/drbd0;
> disk /dev/hde1;
> meta-disk internal;
> address 10.0.1.37:7788;
> }
> on Pacifica-R {
> device /dev/drbd0;
> disk /dev/hdc;
> meta-disk internal;
> address 10.0.1.38:7788;
> }
> }
NB. Pacific-r (10.0.1.38) doesn't exist - yet.
When I start drbd I get:
> Starting DRBD resources: [ d0 s0 n0 ].
> ***************************************************************
> DRBD's startup script waits for the peer node(s) to appear.
> - In case this node was already a degraded cluster before the
> reboot the timeout is 0 seconds. [degr-wfc-timeout]
> - If the peer was available before the reboot the timeout will
> expire after 0 seconds. [wfc-timeout]
> (These values are for resource 'r0'; 0 sec -> wait forever)
> To abort waiting enter 'yes' [ 6]:yes
>
As you see I typed yes to the question.
ps ax shows:
> 15810 ? S 0:00 [drbd0_worker]
> 15823 ? S 0:00 [drbd0_receiver]
/etc/init.d/drbd status shows:
> drbd driver loaded OK; device status:
> version: 0.7.10 (api:77/proto:74)
> SVN Revision: 1743 build by phil at mescal, 2005-01-31 12:22:07
> 0: cs:WFConnection st:Secondary/Unknown ld:Inconsistent
> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
I added the following line to fstab
> /dev/drbd0 /home auto defaults,noauto 0 0
Apparently, as I understand, if everything is OK, I should create a
file system on /dev/drbd0 and then mount it.
But I can't create any filesystems on drbd0 nor can I mount it. So,
what is it that I am missing?
Thanks for any input.
Curtis