Re: vos release stops at 2^64 packets sent.
Mark Vitale <[email protected]>
| Newsgroups | gmane.comp.file-systems.openafs.general |
|---|---|
| Message-ID | <[email protected]> |
> On 27 Jun 2022, at 3:18 PM, Richard Brittain <[email protected]> wrote: > > I know this is a long shot, but I've got a no-quota volume of approx 6TB, and I'm trying to replicate it. It appears to be going fine until the packetRead counter reaches 2^64 and then it stops (doesn't abort). Are you sure it's 2^64? The rx_call->rnext member is the source of the packetRead counter, and it is type afs_uint32, so it should roll over at 2^32 (4294967296 packets). As far as I can tell, nothing would change in this regard in 1.8.x. However, that should be plenty to move 6TB at 800-1400 bytes per packet. So maybe something else is going on - a loop in the dump perhaps, or something else. Just to get things started, could you please issue the following to check the relevant MTUs for the source and target volservers: $ rxdebug <sourcevolserver> 7005 -noconn -peers -onlyport 7005 $ rxdebug <targetvolserver> 7005 -noconn -peers -onlyport 7005 > Servers are 1.6.22 (I thought I'd retire then before now, so didn't bother upgrading to 1.8.x). If 1.8 might change this limit, I can upgrade, but I didn't find any hints in the release notes. > > Based on how long it ran, my guess is > 5TB was transferred. > Is this affected by volser buffer sizes ? I don't know the answer to this off the top of my head; perhaps some others on the list can chime in. Or I may think of something else after I sleep on it. Regards, -- Mark Vitale Sine Nomine Associates