On 6/1/2017 7:43 AM, Andreas Breitfeld wrote: > Hello, > > 'vos move' of a big volume (8.7TB) id 537070263 failed with reporting > the following messages in VolserLog on the target server: > > ### > Tue May 30 11:41:49 2017 1 Volser: WriteFile: Error reading dump file > 171404 size=240744204 nbytes=215734028 (0 of 8192): File exists; restore > aborted
The target server is reporting that it is attempting to read 8K from the incoming rx_call but received 0 bytes. The "File exists" is a red herring because 'errno' is not set by rx. You need to look at the source server to determine why the call ended. Have you moved this volume in the past? I ask because an 8.7TB volume exceeds the maximum safe volume size in OpenAFS (2TB - 1) by quite a bit. Values such as disk usage, file count, and others are signed 32-bit integers that can overflow. While the volume remains in place OpenAFS servers will happily serve the data but it is possible that the volume can no longer be represented by the dump format and that the salvager can no longer reference all of the vnodes that are present in the volume. Jeffrey Altman
<<attachment: jaltman.vcf>>
smime.p7s
Description: S/MIME Cryptographic Signature
