When doing a backup with the AFS 1.2.13 backup system, some volume sizes are obviously displayed erroneous. However, a restore of such a volume succeeds.
Case 1: A volume with approximately 2.3GB was dumped. After a "backup dumpinfo -id 1123250981", I get the following:
38 08/05/2005 16:08 2390479209 home.xyz.backup
which seems to be correct. However, when I do a "backup dumpinfo -id 1123250981 -verbose", I get a negative nBytes report.
Volume ------ name = home.xyz.backup flags = 0x18: First fragment: Last fragment id = 536870923 server = partition = 0 tapeSeq = 1 position = 38 clone = Fri Aug 5 16:08:41 2005 startByte = 0 nBytes = -1904488087 seq = 0 dump = 1123250981 tape = everything.weekly.1
Case 2: When dumping a volume with approximately 8.7GB, and doing a "backup dumpinfo -id 1123250981"
49 08/05/2005 16:08 175847664 local.sl3.readonly
is reported. The size reported here is 175MB which is ways too little. For the "-verbose" version, I get the same wrong report for nBytes.
Volume ------ name = local.sl3.readonly flags = 0x18: First fragment: Last fragment id = 536870949 server = partition = 0 tapeSeq = 1 position = 49 clone = Fri Aug 5 16:08:28 2005 startByte = 0 nBytes = 175847664 seq = 0 dump = 1123250981 tape = everything.weekly.1
Any Ideas / Fixes available? _______________________________________________ OpenAFS-devel mailing list OpenAFS-devel@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-devel
