Hi Dan,
Thanks for the reply.
Another question, is there any different where I run the drbdadm verify
<resource> ? Or I should always run on secondary server?
Regards
Louis
>________________________________
>From: Dan Barker <[email protected]>
>To: [email protected]
>Sent: Thursday, October 6, 2011 4:50 PM
>Subject: RE: [DRBD-user] Online Verification
>
>
>No, on the secondary do a drbdadm <resource> disconnect and then a reconnect.
>The “reconnection” starts the resync. Note, if you are dual primary, it won’t
>resync. That would require demoting a node to secondary, disconnect, connect,
>primary.
>
>Dan
>
>From:[email protected]
>[mailto:[email protected]] On Behalf Of
>[email protected]
>Sent: Thursday, October 06, 2011 10:15 AM
>To: DRBD
>Subject: [DRBD-user] Online Verification
>
>Hi,
>
>I did the online verifcation, and from the log I can see it is out of sync, so
>my question is will drbd automatically resync it after online verification?
>
>Here is my log:
>
>Oct 6 13:07:50 server4 kernel: block drbd3: Starting Online Verify from
>sector 0
>Oct 6 13:14:54 server4 kernel: ata1.00: exception Emask 0x50 SAct 0x0 SErr
>0x90a02 action 0xe frozen
>Oct 6 13:14:54 server4 kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed
>Oct 6 13:14:54 server4 kernel: ata1: SError: { RecovComm Persist HostInt
>PHYRdyChg 10B8B }
>Oct 6 13:14:54 server4 kernel: ata1.00: cmd
>ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
>Oct 6 13:14:54 server4 kernel: res
>40/00:54:a4:fc:fb/00:00:1d:00:00/40 Emask 0x50 (ATA bus error)
>Oct 6 13:14:54 server4 kernel: ata1.00: status: { DRDY }
>Oct 6 13:14:54 server4 kernel: ata1: hard resetting link
>Oct 6 13:15:00 server4 kernel: ata1: softreset failed (device not ready)
>Oct 6 13:15:00 server4 kernel: ata1: failed due to HW bug, retry pmp=0
>Oct 6 13:15:01 server4 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123
>SControl 300)
>Oct 6 13:15:01 server4 kernel: ata1.00: configured for UDMA/133
>Oct 6 13:15:01 server4 kernel: ata1: EH complete
>Oct 6 13:15:01 server4 kernel: SCSI device sda: 976773168 512-byte hdwr
>sectors (500108 MB)
>Oct 6 13:15:01 server4 kernel: sda: Write Protect is off
>Oct 6 13:15:01 server4 kernel: SCSI device sda: drive cache: write back
>Oct 6 13:26:57 server4 kernel: block drbd3: Out of sync: start=56079768,
>size=8 (sectors)
>Oct 6 13:26:59 server4 kernel: block drbd3: Out of sync: start=56161688,
>size=8 (sectors)
>Oct 6 13:43:36 server4 kernel: block drbd3: Online verify done (total 2145
>sec; paused 0 sec; 24440 K/sec)
>Oct 6 13:43:36 server4 kernel: block drbd3: Online verify found 2 4k block
>out of sync!
>Oct 6 13:43:36 server4 kernel: block drbd3: conn( VerifyS -> Connected )
>Oct 6 13:43:36 server4 kernel: block drbd3: Writing the whole bitmap, due to
>failed kmalloc
>Oct 6 13:43:36 server4 kernel: block drbd3: helper command: /sbin/drbdadm
>out-of-sync minor-3
>Oct 6 13:43:36 server4 kernel: block drbd3: helper command: /sbin/drbdadm
>out-of-sync minor-3 exit code 0 (0x0)
>Oct 6 13:43:36 server4 kernel: block drbd3: 8 KB (2 bits) marked out-of-sync
>by on disk bit-map.
>
>
>Regards
>Louis
>
>_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
