Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Mon, Sep 24, 2012 at 08:29:35AM -0500, Shaun Thomas wrote: > On 09/23/2012 05:18 AM, Markus Müller wrote: > As such, we've been avoiding using verify at all, because in the 8.3.x > trees, using it often caused DRBD to hang and require a full system > reboot because the kernel module would become completely unresponsive. Forced disconnect should have been good enough. This may be a known issue (a distributed deadlock) which can happen if your "max-buffers" is too small wrt. your resync rate. > I haven't had any problems with it in 8.4 yet, Which uses the dynamically adaptive resync-rate controller by default, so most of the time will throttle in time, before this can even trigger. Still, the recommended work-around would be to increase the max-buffers setting, or/and increase the allowed/requested tcp socket buffer sizes. > but I'm still a little skittish around > the command in general. > > I've been invalidating hosts I know are bad. I too, would like to > see verify become reliable and useful long term. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed