[DRBD-user] Re: can't create meta data

dp dp7885 at yahoo.com
Sat Aug 12 23:50:19 CEST 2006

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


Here's some more information for this:  The following lines appear in 
/var/log/messages when the recognition of meta data fails.

(By the way, I was successful in building the drivers and creating the 
same drbd0 device under the 7.21 version, although you can't do 2 
primaries with that one.  The drbdmeta call doesn't seem to happen the 
same way, I guess it's all part of the drbdsetup that you have to do 
instead)

I still don't understand what I'm doing wrong.  Anybody got any ideas?

Aug 12 16:31:11 amber kernel: drbd: initialised. Version: 8.0pre4 
(api:83/proto:82)
Aug 12 16:31:11 amber kernel: drbd: SVN Revision: 2316 build by 
root at amber.pickerill.net, 2006-08-12 15:02:00
Aug 12 16:31:11 amber kernel: drbd: registered as block device major 147
Aug 12 16:32:10 amber kernel: drbd0: disk( Diskless -> Attaching )
Aug 12 16:32:10 amber kernel: drbd0: unexpected md_size: 262144 
(expected 305172)
Aug 12 16:32:10 amber kernel: drbd0: disk( Attaching -> Diskless )
Aug 12 16:32:10 amber kernel: drbd0: worker terminated
Aug 12 16:32:10 amber kernel: drbd0: drbd_bm_resize called with capacity 
== 0


-dp- wrote:
> Ok, lets try this again...
> 
> downloaded 08pre4 and built and installed it...
> 
> here's my config
> 
> [root at amber etc]# uname -r
> 2.6.17-1.2157_FC5
> 
> [root at amber etc]# /etc/init.d/drbd status
> drbd driver loaded OK; device status:
> version: 8.0pre4 (api:83/proto:82)
> SVN Revision: 2316 build by 
> root at amber.pickerill.net, 2006-08-05 14:21:43
>  0: cs:Unconfigured
> 
> [root at amber etc]# cat /proc/drbd
> version: 8.0pre4 (api:83/proto:82)
> SVN Revision: 2316 build by 
> root at amber.pickerill.net, 2006-08-05 14:21:43
>  0: cs:Unconfigured
> 
> [root at amber etc]# drbdadm dump
> common {
>     syncer {
>         rate             10M;
>     }
> }
> 
> resource drbd0 {
>     protocol               C;
>     on amber.pickerill.net {
>         device           /dev/drbd0;
>         disk             /dev/sda1;
>         address          192.168.1.4:7788;
>         meta-disk        /dev/sda2 [0];
>     }
>     on avalon.pickerill.net {
>         device           /dev/drbd0;
>         disk             /dev/sda1;
>         address          192.168.1.6:7788;
>         meta-disk        /dev/sda2 [0];
>     }
>     net {
>         after-sb-0pri    disconnect;
>         after-sb-1pri    disconnect;
>         after-sb-2pri    disconnect;
>     }
>     disk {
>         on-io-error      detach;
>     }
>     syncer {
>         rate             10M;
>         al-extents       257;
>     }
>     startup {
>         degr-wfc-timeout 120;
>     }
>     handlers {
>         pri-on-incon-degr "halt -f";
>         pri-lost-after-sb "halt -f";
>     }
> }
> 
> 
> Now here's what happens...
> 
> [root at amber etc]# drbdadm create-md all
> 
> Valid meta-data already in place, recreate new?
> [need to type 'yes' to confirm] yes
> 
> Creating meta data...
> initialising activity log
> initialising bitmap (131036 KB)
> 99%New drbd meta data block sucessfully created.
> [root at amber etc]# drbdadm up all
> ioctl(,SET_DISK_CONFIG,) failed: Invalid argument
> No valid meta-data signature found.
> Use 'drbdadm create-md res' to initialize meta-data area.
> 
> Command 'drbdsetup /dev/drbd0 disk /dev/sda1 /dev/sda2 0 
> --on-io-error=detach' terminated with exit code 20
> 
> 
> What am I missing or doing wrong?
> 
> -dp-




More information about the drbd-user mailing list