[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amanda-users
Subject:    Re: Problems backing up
From:       "John R. Jackson" <jrj () gandalf ! cc ! purdue ! edu>
Date:       2001-06-29 18:27:25
[Download RAW message or body]

>Does this help any further?  ...

Not really.

>or is there any way in which I can see at which
>particular file it hangs itself?

It's not necessarily hanging on a particular file.  It could be that
after some "random" period, your network dies (for that connection),
or any number of other problems.

The file in the holding disk should be accurate to within 32 KBytes
of what GNU tar has done so far (unless you have software compression
enabled).  So one way to see roughly where it is would be generate your
own catalogue:

  amrestore -p /path/to/holding/disk/file cobalt01 | gtar tvf -

If you have multiple holding disk chunks for this disk, use the one
with the shortest name (the one that does *not* have the .1, .2, .3
type suffixes).

You could also install lsof (ftp://vic.cc.purdue.edu/pub/tools/unix/lsof
or it's available from various places pre-built) and run it on the
GNU tar.  That should tell you what it has open.

John R. Jackson, Technical Software Specialist, jrj@purdue.edu

P.S.  Please turn off "send as HTML" in your mailer.  It's just a waste
of bandwidth.

[prev in list] [next in list] [prev in thread] [next in thread]