Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Thu, Apr 21, 2016 at 10:01:12PM +1000, Adam Goryachev wrote:
> Hi,
>
> I've found another issue with (my system or) the DRBD docs:
> http://www.drbd.org/en/doc/users-guide-90/s-check-status
>
> >You can get more information by passing the |--verbose| and/or
> >|--statistics| arguments:
> >
> ># drbdadm status home --verbose --statistics
> Except this happens:
> castle:~# drbdadm status oldNFS --verbose --statistics
please use:
# drbdsetup status oldNFS --verbose --statistics
> While we are at it, I would appreciate if you can provide any tips
> on how to determine why the volume is "outdated"
hard to guess.
may be normal behaviour, may be a bug.
> and how I can change it back to a working state?
usually, a resync triggered by disconnect/reconnect should help.
if not, maybe an explicit "primary" or even "primary --force".
> I'm not entirely concerned about the content if it is not
> recoverable, but in case this happens later with more important data
> then it would be good to know the right procedure to recovery.
Lars