Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
As a followup, Im also seeing a lot of stalled on the LAN using Protocol A and I set syncer to 100k or 150k. When I goto drbdadm down all. I get the drbd is not loaded and I have to do a reboot in order to get control of it again. (A kill would probably work too) Running FC7 2.6.21-1.3194.fc7 (default from the fc7 iso) everything looks like it installed ok and it works perfect in C but in A will get this 'stall' message a lot of the time after just 20-30 mins of throwing data on and off the primary. From: drbd-user-bounces at lists.linbit.com [mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of Benjamin Zachary Sent: Wednesday, November 14, 2007 2:50 AM To: drbd-user at lists.linbit.com Subject: [DRBD-user] Following Up Well ive been playing with the product for a few weeks and it works great on the LAN. I tried setting virtual boundaries and lowering the speed to 100k and setting Protocol to A and I was wondering how far can one device 'fall behind' before it may lose the ability to sync. For example, Im maintaining a 2TB device but have my drbd on the WAN link which is 3Meg pipe (2 bonded T1s) obviously the data will never be able to keep up with the writes during the day but at night when the business slows to a crawl I should be able to 'catch up' as long as the system doesn't lose track of where it is. I was trying to look at the conf and a few other things seeing if there was a way to manage that (including how to tell if the buffer is near being full etc) or at least see it. Thx -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20071114/42fe17c3/attachment.htm>