|
Re: Problem Backing Up NFS SmartStor
2008-08-26 13:14:29
Still looks like a general NFS time out, see anything in the system
logs on any of these machines (or the SmartStor?)? Also, are you
trying dump or tar to back these up? Dump might have issues over the
NFS Mount...
You might also think about an alternate approach: mount all of these
RO on the backup server and back them up directly, instead of NFS to
the host and amanda to the server. You're creating more network
traffic than you really need this way, I'd think. It might give you
some issues if you're dumping more than one of them at the same time,
as you get a lot of network traffic and possible delays off the disk
on the SmartStor.
-Darrell
On Aug 25, 2008, at 11:40 AM, Steven Backus wrote:
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
|
|
|
