> How many backups are/were you running in parallel?
Typically 4. But when I switched everything to rsync I wanted fulls done on all the pc's so I was running up to 8 at a time.
> I think that segfault in a perl process needs to be tracked down before expecting anything else to make sense.
> Either bad RAM or mismatching perl libs could break about anything else.
I installed perl-libs with yum as well. A yum info perl-libs tells me it was installed from the updates repo
I think what I'm going to try at this point is to delete the bad backups, reinstall perl from epel, and keep an eye on it to see if it balloons up again. Thanks for all your help!
In my experience, segfault in libraries usually caused by installing it from different source.
For example, when I install BackupPC for CentOS, I use the one in EPEL repo.
I make sure that all the libraries (perl and others), only come from CentOS base repo, and not from other, as installing them from somewhere else might cause incompatibilities.
In fact, sometime EPEL repo also provide perl library that conflict with CentOS base repo, but I just ignore it, and stick to base repo.
On Thu, Oct 31, 2013 at 2:20 PM, Holger Parplies <wbppc AT parplies DOT de> wrote:
>>
> That doesn't explain your situation, but it still might be something to think
> about (and we might be seeing one problem on top of and as result of another).
> I agree with Jeffrey - an "Unable to read ..." error *without* a preceeding
> "Can't write len=... to .../RStmp" sounds like a mismatch between file length
> according to attrib file and result of decompression of compressed file -
> probably caused by corruption of the compressed file (or the attrib file,
> though unlikely, because the size is not "way off").
I think that segfault in a perl process needs to be tracked down
before expecting anything else to make sense. Either bad RAM or
mismatching perl libs could break about anything else.
--
Les Mikesell lesmikesell AT gmail DOT com
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
