On Wed, 2010-05-05 at 10:16 -0500, Dustin J. Mitchell wrote:
> On Wed, May 5, 2010 at 3:55 AM, Mark Adams wrote:
> > Why would the file not be in the archive if it is showing in the index?
> > Is there anything else I can try before I try to retrieve the whole DLE?
>
> So this is a new dump? No
On Wed, May 5, 2010 at 2:10 PM, Jean-Francois Malouin
wrote:
> I've corrected this by using the same state file in both
> child-changer. I'm now experiencing other problems, maybe due to some
> mis-config from my part:
>
> ~# su amanda -c "/opt/amanda-3.1.0beta2/sbin/amtape rait taper"
> slot ?: f
Dustin,
On Wed, May 05, 2010 at 02:09:40PM -0500, Dustin J. Mitchell wrote:
> On Wed, May 5, 2010 at 1:38 PM, Brian Cuttler wrote:
> > Also, the issues seem to be specific to certain DLE, in both
> > cases the busiest of the DLEs, not necessarily the largest
> > but the most active.
>
> It's cle
* Dustin J. Mitchell [20100504 18:53]:
> On Tue, May 4, 2010 at 4:44 PM, Jean-Francois Malouin
> wrote:
> > One question: should the changerfile parameter for chg-robot point to
> > the same file for both child-changers:
>
> Yes, it should - that will allow the changers to avoid stepping on each
On Wed, May 5, 2010 at 1:38 PM, Brian Cuttler wrote:
> Also, the issues seem to be specific to certain DLE, in both
> cases the busiest of the DLEs, not necessarily the largest
> but the most active.
It's clearly timing-related, then. Keep in mind that hte dtimeout is
a timeout without *any* dat
Darin,
On Wed, May 05, 2010 at 02:19:35PM -0400, Darin Perusich wrote:
> Brian,
>
> I've found that on systems with alot of ZFS file systems I needed to
> increase the {e,d,c}timeout values. Below are the values I have set and
> I'm backing up some 150+ ZFS filesystems of varying sizes from a sin
Brian,
I've found that on systems with alot of ZFS file systems I needed to
increase the {e,d,c}timeout values. Below are the values I have set and
I'm backing up some 150+ ZFS filesystems of varying sizes from a single
server, dumps are a mixture of suntar and zfs-sendrecv.
etimeout 1600
dtimeou
Dustin,
Dan,
I wondered about dtimout, but we have a very similar issue
on another system and I tried that.
In both cases the DLE with the problem is the largest, no
not the largest - the most active ZFS mountpoint on the box.
The other DLEs have no issues, not even intermittently and
raising t
What is the error? I suspect this:
1273071472.718696: dumper: security_seterror(handle=8074f08,
driver=fef09394 (BSD) error=timeout waiting for REP)
which likely means that you're exceeding the dtimeout for that DLE for
whatever reason. Try increasing that?
Dustin
--
Open Source Storage Engi
On Wed, May 5, 2010 at 3:55 AM, Mark Adams wrote:
> Why would the file not be in the archive if it is showing in the index?
> Is there anything else I can try before I try to retrieve the whole DLE?
So this is a new dump? No, I can't see any reason it would do that.
Hopefully retrieving the enti
Hi All,
I've run this backup again with smaller chunks (40Gb, not that this
should make a difference?) and it is now saying it can't find anything I
try to recover in the archive.
tar: ./path/here/IMG_4254.jpg: Not found in archive
tar: Error exit delayed from previous errors
Why would the file
11 matches
Mail list logo