> amanda 29620 29614 3 13:12:42 pts/13 0:27 cat
This says it was collecting the rest of the file from tape and throwing
it away (which is normal).
>Checked sundev1.corp.walid.com.c0t0d0s7.20010113.0
>Reading...
As does this.
>I guess the image Check on sundev1.corp.walid.com.c0t0d0s7.20010113.0
>was what took so long? thoughts...
What thoughts are you looking for?
How big was the image? How fast is your tape drive? Was the image
compressed? How busy was the system when you were running amverify?
>lsof:
>We tried to get lsof installed on our solaris box 2 months ago but it
>failed to run after the install - we got a 32/64 bit error message.
I assume you then contacted the author (who happens to be my boss) and
he got it fixed for you, right? That program runs on bajillions of OS's
and versions. It would be truly amazing if it does not work at your site.
>More importantly - since amverify is failing - does that imply I will
>not be able to amrestore/amrecover the image
>sundev1.corp.walid.com.c0t0d0s7.20010113.0 on this tape?
No. First, amverify is not failing (as you now know). However, if it
had with an I/O error or some kind of consistency failure from your dump
program, that may or may not mean you would be able to restore at least
some of the files. Or it could have been a dirty drive, etc.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
