Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 2011-10-06 16:14, mailtolouis2020-forum at yahoo.com wrote:
> 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?
As it verifies, for any out-of-sync block it finds DRBD sets the
corresponding bit in the quick-sync bit map. Then, whenever a resync
runs, those out-of-sync blocks are included in the sync data set. You
can then tickle DRBD into starting a resync by disconnect/connect. All
of this is explained in detail at
http://www.drbd.org/users-guide/s-use-online-verify.html.
> 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)
You probably really want to fix your storage.
Florian
--
Need help with DRBD?
http://www.hastexo.com/now