|
Re: sendbackup: index tee cannot write [Broken pipe]
2007-03-07 04:23:24
A few days ago I had some backup problems that turned out to be caused
by a hanging NFS mount, causing "sendsize" to lock up completely - see
a separate post on this. Now I have sorted out this problem, and it
seemed like amdump would once again start properly, but it turns out
that the backup still doesn't run properly - this time it's
"sendbackup" that gets into trouble. The full sendbackup...debug from
a failed dump is included below. [ ... ]
Right. After looking a bit more at the logs etc. I'm no longer convinced
that the error reported here is the main issue, and that it could be
caused by a full disk - which I didn't think at first it might be,
because I though I got the same behaviour for different configs with
different holding space on different disks and I was convinced that they
can't all have been filled up.
Anyhow, the thing is, I've been getting the following strange and
somewhat annoying (because I just can't understand what "stranded on
waitq" is supposed to mean) error message:
fileserv:/archive 0 planner: [hmm, disk was
stranded on waitq]
This turned out to be caused by various sendsize processes hanging
because of NFS access problems. Or at least, so I thought, but after
sorting out these issues, I still get the same message. So I looked at
the logs again and noticed the "index tee cannot write", but maybe it's
just a coincidence that this started occurring right now, and that the
other message is caused by something else entirely?
- Toralf
|
|
|
