Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello,
I'm in uncharted territory but I figured this issue has come up a lot so I wanted to see exactly how to handle. I have a two node DRBD setup. Our primary went down and our secondary was put into primary status. I've rebuilt the server and now have to bring it up as secondary mode. The DRBD is running in a XEN VM. I created XVDB and attached using the following two commands:
dd if=/dev/zero of=xvdb bs=1M count=303104
xm block-attach fs0 file://mn/fs0/xvdb /dev/xvdb w
I can see this device in the DRBD instance. Network is setup fine, no firewall issues present and configuration matches what is currently on our current DRBD primary (very simple, pretty much matches the manual's example). Using the DRBD manual, on our newly restored instance, I enabled my resource for the first time with create-md, attach, syncer, and connect. All went without issue. I ran the
drbdadm -- --overwrite-data-of-peer primary resource
and noticed in drbd-overview the following output on primary
1:r0 StandAlone Primary/Unknown UpToDate/DUnknown r---- /mnfs ext4 296G 129G 152G 46%
On secondary (recently rebuilt node) I have the following:
1:r0 WFConnection Secondary/Unknown Inconsistent/DUnknown C r----
Checked system log and I have the following (asterisk denote what I believe to be issue) :
Jun 15 15:04:13 mnfs1 kernel: [13135515.447461] block drbd1: conn( StandAlone -> Unconnected )
Jun 15 15:04:13 mnfs1 kernel: [13135515.447564] block drbd1: Starting receiver thread (from drbd1_worker [2375])
Jun 15 15:04:13 mnfs1 kernel: [13135515.447665] block drbd1: receiver (re)started
Jun 15 15:04:13 mnfs1 kernel: [13135515.447671] block drbd1: conn( Unconnected -> WFConnection )
Jun 15 15:04:13 mnfs1 kernel: [13135515.545575] block drbd1: Handshake successful: Agreed network protocol version 92
Jun 15 15:04:13 mnfs1 kernel: [13135515.545601] block drbd1: conn( WFConnection -> WFReportParams )
Jun 15 15:04:13 mnfs1 kernel: [13135515.545619] block drbd1: Starting asender thread (from drbd1_receiver [23493])
Jun 15 15:04:13 mnfs1 kernel: [13135515.545883] block drbd1: data-integrity-alg: <not-used>
**** Jun 15 15:04:13 mnfs1 kernel: [13135515.545889] block drbd1: The peer's disk size is too small!
Jun 15 15:04:13 mnfs1 kernel: [13135515.545893] block drbd1: conn( WFReportParams -> Disconnecting )
Jun 15 15:04:13 mnfs1 kernel: [13135515.545898] block drbd1: error receiving ReportSizes, l: 32!
Jun 15 15:04:13 mnfs1 kernel: [13135515.545979] block drbd1: asender terminated
Jun 15 15:04:13 mnfs1 kernel: [13135515.545989] block drbd1: Terminating drbd1_asender
Jun 15 15:04:13 mnfs1 kernel: [13135515.546125] block drbd1: Connection closed
Jun 15 15:04:13 mnfs1 kernel: [13135515.546133] block drbd1: conn( Disconnecting -> StandAlone )
Jun 15 15:04:13 mnfs1 kernel: [13135515.546142] block drbd1: receiver terminated
Jun 15 15:04:13 mnfs1 kernel: [13135515.546144] block drbd1: Terminating drbd1_receiver
Run of cat /proc/drbd on both nodes results to
--Current Primary--
version: 8.3.7 (api:88/proto:86-92)
srcversion: 04F43AA72D62F7D4F0CB048
1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----
ns:0 nr:0 dw:94736400 dr:51827661 al:32314 bm:2203 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:3459476
--Current Secondary-
version: 8.3.7 (api:88/proto:86-92)
srcversion: 04F43AA72D62F7D4F0CB048
1: cs:WFConnection ro:Secondary/Unknown ds:Inconsistent/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:310368988
Again, I see the file size on my newly built instance is no bueno. Am I missing something? How can I get this filesystem to actually report the actual size.
One more note:
A quick run of fdisk -l on both systems results in this:
--Current Primary--
Disk /dev/xvdb: 322.1 GB, 322122547200 bytes
255 heads, 63 sectors/track, 39162 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/xvdb doesn't contain a valid partition table
--Current Secondary (rebuilt vm instance)-
Disk /dev/xvdb: 317.8 GB, 317827579904 bytes
255 heads, 63 sectors/track, 38640 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/xvdb doesn't contain a valid partition table
(One note I just noticed, do the /dev/xvdb need to be the same size?)
Thanks
Jason
[cid:image001.png at 01CC2B71.EB95E5B0]
Jason Huselton
Network Administrator
Direct: (832) 532-7220
Mobile: (281) 725-2490
[cid:image002.png at 01CC2B71.EB95E5B0]<http://www.facebook.com/earthsports>[cid:image003.png at 01CC2B71.EB95E5B0]<http://www.linkedin.com/in/jhuselton>[cid:image004.png at 01CC2B71.EB95E5B0]<http://www.youtube.com/user/earthsportstv>[cid:image005.png at 01CC2B71.EB95E5B0]<http://twitter.com/earthsports>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110615/b57708ca/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 17328 bytes
Desc: image001.png
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110615/b57708ca/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1541 bytes
Desc: image002.png
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110615/b57708ca/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1619 bytes
Desc: image003.png
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110615/b57708ca/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1942 bytes
Desc: image004.png
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110615/b57708ca/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 2329 bytes
Desc: image005.png
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110615/b57708ca/attachment-0004.png>