On 2017-11-14 07:34, Austin S. Hemmelgarn wrote:
On 2017-11-13 16:42, Jean-Louis Martineau wrote:
On 13/11/17 02:53 PM, Austin S. Hemmelgarn wrote:
driver: send-cmd time 9300.326 to taper1: VAULT-WRITE worker1-0
00-00120 local-vtl local-vtl Home-0001 client0 /home/1D 0
20171113073255 "" "" "" "" 1073741824 memory "" "" 0
> FAIL taper "ST:cloud" "POOL:cloud" client0 /home/1D 20171113073255
0 error "File 0 not found"
Do that dump still exists on tape Home-0001? Find it with amfetchdump.
If yes, send me the taper debug file.
amfetchdump does not see it, but looking directly at the virtual tape
directories, I can see it there.
Just tried an amcheckdump on everything, it looks like some of the dump
files are corrupted, but I can't for the life of me figure out why (I
test our network regularly and it has no problems, and any problems with
a particular system should show up as more than just corrupted tar
files). I'm going to try disabling compression and see if that helps at
all, as that's the only processing other than the default that we're
doing on the dumps (long term, it's not really a viable option, but if
it fixes things at least we know what's broken).
