Amanda-Users

Re: Problem Backing Up NFS SmartStor

2008-08-25 13:36:07
Subject: Re: Problem Backing Up NFS SmartStor
From: Steven Backus <backus AT whimsy.med.utah DOT edu>
To: on AT cs.ait.ac DOT th (Olivier Nicole)
Date: Mon, 25 Aug 2008 10:40:51 -0600 (MDT)
Long ago, I wrote:

> >   I have a Promise SmartStor, a network drive.  It's NFS mounted on
> > a Red Hat server.  Sometimes it gets backed up, other times I get:
> > 
> >   whimsy.med.utah.edu    /sstore/9gb  lev 0  FAILED [dumper returned FAILED]
> >   whimsy.med.utah.edu    /sstore/9gb  lev 0  FAILED [data timeout]
> >   whimsy.med.utah.edu    /sstore/9gb  lev 0  FAILED [cannot read header: 
> > got 0 instead of 32768]
> >   whimsy.med.utah.edu    /sstore/9gb  lev 0  FAILED [too many dumper retry: 
> > "[request failed: timeout waiting for REP]"]
> 

Olivier Nicole <on AT cs.ait.ac DOT th> then wrote:

> Just a wild guess, but a Google search yesterday on "cannot read
> header: got 0 instead of " lead me to problems with IPv6/IPv4.

So this didn't help, today I got:

  whimsy.med.utah.edu    /sstore/gen6   lev 2  FAILED [dumper returned FAILED]
  clarity.med.utah.edu   /sstore/gen10  lev 0  FAILED [data timeout]
  clarity.med.utah.edu   /sstore/gen10  lev 0  FAILED [dumper returned FAILED]
  whimsy.med.utah.edu    /sstore/gen6   lev 2  FAILED [too many dumper retry: 
"[request failed: timeout waiting for REP]"]
  whimsy.med.utah.edu    /sstore/gen6   lev 2  FAILED [cannot read header: got 
0 instead of 32768]
  clarity.med.utah.edu   /sstore/gen10  lev 0  FAILED [cannot read header: got 
0 instead of 32768]
  clarity.med.utah.edu   /sstore/gen10  lev 0  FAILED [too many dumper retry: 
"[request failed: timeout waiting for REP]"]
  serenity.med.utah.edu  /sstore/9gb    lev 1  FAILED [data timeout]
  serenity.med.utah.edu  /sstore/9gb    lev 1  FAILED [dumper returned FAILED]
  serenity.med.utah.edu  /sstore/9gb    lev 1  FAILED [cannot read header: got 
0 instead of 32768]
  serenity.med.utah.edu  /sstore/9gb    lev 1  FAILED [too many dumper retry: 
"[request failed: timeout waiting for REP]"]

i.e., problems with all the file systems on this drive.  I have my
timeouts set to:

etimeout                100000
dtimeout                3600
ctimeout                60

Should I increase them?  Which one?  Any other ideas?

Thanks,
  Steve
-- 
Steven J. Backus                        Computer Specialist
University of Utah                      E-Mail:  steven.backus AT utah DOT edu
Genetic Epidemiology                    Alternate:  backus AT math.utah DOT edu
391 Chipeta Way -- Suite D              Office:  801.587.9308
Salt Lake City, UT 84108-1266           http://www.math.utah.edu/~backus

<Prev in Thread] Current Thread [Next in Thread>