Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
We have installed DRBD 8.3.7, and have created an apparently working 3 node
replication:
[root at sweng65 ~]# cat /proc/drbd
version: 8.3.7 (api:88/proto:86-91)
srcversion: EE47D8BF18AC166BE219757
0: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r----
ns:1081851 nr:0 dw:33447 dr:2097076 al:13 bm:64 lo:0 pe:0 ua:0 ap:0 ep:1
wo:b oos:0
1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r----
ns:1081740 nr:0 dw:33300 dr:1048477 al:13 bm:64 lo:0 pe:0 ua:0 ap:0 ep:1
wo:b oos:0
On the stacked primary resource we have created an ext3 file system via:
'mkfs.ext3 /dev/drbd1'
Our Primary/secondary resource is on /dev/drbd0.
To test truck replication from the remote backup mirror, we have stopped
drbd on both the primary and secondary servers, then followed the procedure
described here
http://www.drbd.org/users-guide-legacy/s-using-truck-based-replication.html,
using dd to create a bit image copy to a file that we then dd onto the
backing store of the (down) primary server's backing store.
Our attempts to get the primary mirror up look like this (athough the ext3
file system is recovered, most importantly at the moment for us is that the
stacked metadata is missing, and cannot be re-created without shrinking the
ext3 file system ... why would that be true?):
[root at sweng65 ~]# dd if=/pkg/nvs/cores/truck.1008 of=/dev/VG00/mysql bs=256k
4096+0 records in
4096+0 records out
1073741824 bytes (1.1 GB) copied, 6.6437 seconds, 162 MB/s
[root at sweng65 ~]# drbdadm --stacked up r0-U
Can not open device '/dev/drbd0': Read-only file system
Command 'drbdsetup 1 disk /dev/drbd0 /dev/drbd0 internal --set-defaults
--create-device --on-io-error=call-local-io-error' terminated with exit code
20
drbdadm attach r0-U: exited with code 20
[root at sweng65 ~]# drbdadm up r0
[root at sweng65 ~]# drbdadm --stacked up r0-U
Can not open device '/dev/drbd0': Read-only file system
Command 'drbdsetup 1 disk /dev/drbd0 /dev/drbd0 internal --set-defaults
--create-device --on-io-error=call-local-io-error' terminated with exit code
20
drbdadm attach r0-U: exited with code 20
[root at sweng65 ~]# cat /proc/drbd
version: 8.3.7 (api:88/proto:86-91)
srcversion: EE47D8BF18AC166BE219757
0: cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown C r----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
1: cs:Unconfigured
[root at sweng65 ~]# drbdadm primary r0
[root at sweng65 ~]# drbdadm --stacked up r0-U
1: Failure: (119) No valid meta-data signature found.
==> Use 'drbdadm create-md res' to initialize meta-data area. <==
Command 'drbdsetup 1 disk /dev/drbd0 /dev/drbd0 internal --set-defaults
--create-device --on-io-error=call-local-io-error' terminated with exit code
10
[root at sweng65 ~]# drbdadm --stacked create-md r0-U
md_offset 1073598464
al_offset 1073565696
bm_offset 1073532928
Found ext3 filesystem
1048440 kB data area apparently used
1048372 kB left usable by current configuration
Device size would be truncated, which
would corrupt data and result in
'access beyond end of device' errors.
You need to either
* use external meta data (recommended)
* shrink that filesystem first
* zero out the device (destroy the filesystem)
Operation refused.
Command 'drbdmeta 1 v08 /dev/drbd0 internal create-md' terminated with exit
code 40
drbdadm create-md r0-U: exited with code 40
[root at sweng65 ~]# mount -t ext3 /dev/drbd0 /mirror
[root at sweng65 ~]# ls -l /mirror
total 16
drwx------ 2 root root 16384 Aug 4 15:03 lost+found
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110804/17926780/attachment.htm>