> This error shows BackupPC_dump segfault, and pointing to libperl.so
> How do you install your BackupPC ? From source or from RPM?
I did a yum install backuppc, which got it from epel
> That tells you it was unmounted cleanly last time, not that
everything checks out OK.
> Try it with the -f option to make it do the actual checks.
bash-4.1$ fsck -f /dev/sda1
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda1: 20074505/2929688576 files (0.3% non-contiguous),
2775975116/2929686016 blocks
bash-4.1$
> What distro are you using? (I use CentOS/RHEL)
CentosOS release 6.4
> 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!
Regards,
Craig
On Thu, Oct 31, 2013 at 10:09 PM, Sharuzzaman Ahmat Raslan <
sharuzza...@gmail.com> wrote:
> 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 Fri, Nov 1, 2013 at 3:57 AM, Les Mikesell <lesmikes...@gmail.com>wrote:
>
>> On Thu, Oct 31, 2013 at 2:20 PM, Holger Parplies <wb...@parplies.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
>> lesmikes...@gmail.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
>> _______________________________________________
>> BackupPC-users mailing list
>> BackupPC-users@lists.sourceforge.net
>> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
>> Wiki: http://backuppc.wiki.sourceforge.net
>> Project: http://backuppc.sourceforge.net/
>>
>
>
>
> --
> Sharuzzaman Ahmat Raslan
>
>
> ------------------------------------------------------------------------------
> 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
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
>
------------------------------------------------------------------------------
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
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
