Backup Central

Okay, I'm almost ready to give up on rdiff-backup! I really don't to do
so because I really like, but the this problem I've been having is
starting to take a toll on me. Fortunately, I've kind of narrowed the
problem down to the following.

Ok, I have the following source directory


source directory = /home/golden/testy

The contents of /home/golden/testy are:

test.txt
test2.txt
test3.txt

Now, I run

rdiff-backup -v7 --print-statistics /home/golden/testy
/iomega/bkps/loomis/gtest

The backup runs with no problem, this is the first backup into an empty
directory.

Then I modify /home/golden/testy/test.txt by adding a line to the file
and then save it.

Then I run the above rdiff-backup script, the evil happens! Rdiff-backup
fails with the following error:

#####################################################################################3
Unable to import module xattr.
Extended attributes not supported on filesystem at /home/golden/testy
Unable to import module posix1e from pylibacl package.
ACLs not supported on filesystem at /home/golden/testy
-----------------------------------------------------------------
Detected abilities for source (read only) file system:
Access control lists Off
Extended attributes Off
Mac OS X style resource forks Off
Mac OS X Finder information Off
-----------------------------------------------------------------
Making directory
/iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0
Touching /iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/foo
Deleting /iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/foo
Touching
/iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/hardlinked_file1
Hard linking
/iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/hardlinked_file2
to
/iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/hardlinked_file1
Unable to import module xattr.
Extended attributes not supported on filesystem at
/iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0
Unable to import module posix1e from pylibacl package.
ACLs not supported on filesystem at
/iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0
Touching
/iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/dir_inc_check
Deleting
/iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/dir_inc_check
Touching
/iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/regfile
Deleting
/iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/regfile
Touching
/iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/5-_ a.
Deleting
/iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/5-_ a.
Touching /iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/A
Deleting /iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/A
Touching /iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/:
Deleting /iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/:
Touching /iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/\
Deleting /iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/\
Touching /iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/�
Deleting /iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0/�
Deleting /iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0
Removing directory
/iomega/bkps/loomis/gtest/rdiff-backup-data/rdiff-backup.tmp.0
-----------------------------------------------------------------
Detected abilities for destination (read/write) file system:
Characters needing quoting ''
Ownership changing On
Hard linking On
fsync() directories On
Directory inc permissions On
Access control lists Off
Extended attributes Off
Mac OS X style resource forks Off
Mac OS X Finder information Off
-----------------------------------------------------------------
Writing mirror marker
/iomega/bkps/loomis/gtest/rdiff-backup-data/current_mirror.2005-10-13T22:46:19-05:00.data
Starting increment operation /home/golden/testy to /iomega/bkps/loomis/gtest
Processing changed file .
Incrementing mirror file /iomega/bkps/loomis/gtest
Touching
/iomega/bkps/loomis/gtest/rdiff-backup-data/increments.2005-10-13T22:45:33-05:00.dir
Copying inc attrs from () to
/iomega/bkps/loomis/gtest/rdiff-backup-data/increments.2005-10-13T22:45:33-05:00.dir
Setting time of
/iomega/bkps/loomis/gtest/rdiff-backup-data/increments.2005-10-13T22:45:33-05:00.dir
to 1129261360
Getting signature of test.txt with blocksize 64
Getting delta of /home/golden/testy/test.txt with signature test.txt
Processing changed file test.txt
Writing file object to /iomega/bkps/loomis/gtest/rdiff-backup.tmp.1
./test-bkp: line 2: 20700 Segmentation fault rdiff-backup -v7
--print-statistics /home/golden/testy
##################################################################################################################

Why would rdiff-backup fail at this point? If I can't get rdiff-backup
to backup a folder with three small text files, how would ever get it
backup up my company's data of over 50 GB? Any help or suggestions is
greatly appreciated.

Thanks,

Golden Delamatrix

Golden Butler wrote:

Why would rdiff-backup fail at this point? If I can't get rdiff-backup
to backup a folder with three small text files, how would ever get it
backup up my company's data of over 50 GB? Any help or suggestions is
greatly appreciated.


Where you using FAT32 on this drive? I don't think rdiff-backup doesn't
work on FAT32. I suggest you use ext3. If you need to be able to read
ext3 on windows there is an excellent ext3 driver for xp and 2000 i think

thanks

dave

Hi,

On Thu, 13 Oct 2005, Golden Butler wrote:

rdiff-backup -v7 --print-statistics /home/golden/testy /iomega/bkps/loomis/gtest

/iomega sounds like you're using some iomega device, which usually use
pre-formatted media using FAT32.

However...

-----------------------------------------------------------------
Detected abilities for destination (read/write) file system:
Characters needing quoting ''
Ownership changing On
Hard linking On
fsync() directories On
Directory inc permissions On
Access control lists Off
Extended attributes Off
Mac OS X style resource forks Off
Mac OS X Finder information Off
-----------------------------------------------------------------

... hardlinking capability on FAT32 seems very unlikely.

So, what exactly is mounted below the iomega directory you're trying to
backup to?

Furthermore: you seem to be trying to backup with root privileges on the
target filesystem. No problem with that, but you might want to try a more
common approach: as a non-privileged user, ssh to root < at > localhost (using an
ssh key and possibly a ~/.ssh/config file to simplify the rdiff-backup
command line) and execute rdiff-backup as if it were running on a
remote host.

Also, you could try a newer rdiff-backup version. I remember there have
been some problems preventing it to run smoothly under certain
circumstances.

Regards,
Maarten Bezemer

Dave and Marteen,

The iomega device I'm using is not formatted as FAT32.  It's partitioned and formatted as reiserfs.  Is this filesystem type not recommended?  Also, I did upgrade rdiff-backup to version 1.0.1 with the same results.   It seems like something fundamental that I'm missing but I can't figure it out.  I really appreciate your guys input.  Any more suggestions of advice?

Golden Delamatrix

Dave Kempe wrote: Golden Butler wrote:

Why would rdiff-backup fail at this point? If I can't get rdiff-backup
to backup a folder with three small text files, how would ever get it
backup up my company's data of over 50 GB? Any help or suggestions is
greatly appreciated.


Where you using FAT32 on this drive? I don't think rdiff-backup doesn't
work on FAT32. I suggest you use ext3. If you need to be able to read
ext3 on windows there is an excellent ext3 driver for xp and 2000 i think

thanks

dave

Dave and Marteen,

The iomega device I'm using is not formatted as FAT32. It's partitioned and formatted as reiserfs. Is this filesystem type not recommended? Also, I did upgrade rdiff-backup to version 1.0.1 with the same results. It seems like something fundamental that I'm missing but I can't figure it out. I really appreciate your guys input. Any more suggestions of advice?

Golden Delamatrix

Dave Kempe wrote: Golden Butler wrote:

Why would rdiff-backup fail at this point? If I can't get rdiff-backup
to backup a folder with three small text files, how would ever get it
backup up my company's data of over 50 GB? Any help or suggestions is
greatly appreciated.


Where you using FAT32 on this drive? I don't think rdiff-backup doesn't
work on FAT32. I suggest you use ext3. If you need to be able to read
ext3 on windows there is an excellent ext3 driver for xp and 2000 i think

thanks

dave

Golden Butler wrote:

Dave and Marteen,

The iomega device I'm using is not formatted as FAT32. It's
partitioned and formatted as reiserfs. Is this filesystem type not
recommended? Also, I did upgrade rdiff-backup to version 1.0.1 with
the same results. It seems like something fundamental that I'm
missing but I can't figure it out. I really appreciate your guys
input. Any more suggestions of advice?


I have been using rdiff-backup for years on many different machines and
scenarios and never had it segfault. I don't understand where that is
coming from. If rdiff-backup crashes it generates the typical python
stack trace. Where exactly is this segfault coming from? maybe its time
to get out strace

dave

I'm still relatively a newbie to linux even though I've been using it for almost two years, so excuse me for the ignorance.  What is "strace", and how would I be able to use to track down this segfault problem?

Delamatrix

Dave Kempe wrote: Golden Butler wrote:

Dave and Marteen,

The iomega device I'm using is not formatted as FAT32. It's
partitioned and formatted as reiserfs. Is this filesystem type not
recommended? Also, I did upgrade rdiff-backup to version 1.0.1 with
the same results. It seems like something fundamental that I'm
missing but I can't figure it out. I really appreciate your guys
input. Any more suggestions of advice?


I have been using rdiff-backup for years on many different machines and
scenarios and never had it segfault. I don't understand where that is
coming from. If rdiff-backup crashes it generates the typical python
stack trace. Where exactly is this segfault coming from? maybe its time
to get out strace

dave

Golden Butler wrote:

I'm still relatively a newbie to linux even though I've been using it
for almost two years, so excuse me for the ignorance. What is
"strace", and how would I be able to use to track down this segfault
problem?


strace follows a program and tracks down system calls etc. Its sometimes
useful, though generates a massive output for most things. If its
install simply doing 'strace command' will give you an idea.

Anyway, its probably not going to help you that much - its output is
pretty confusing.

can you try backing up to and from the same filesystem - ie try
rdiff-backup -v7 /home /tmp/home-backup

dave

I just tried backing up to and from the same filesystem with the the same result, below:

#######################################################
Unable to import module xattr.
Extended attributes not supported on filesystem at /home/golden/testy
Unable to import module posix1e from pylibacl package.
ACLs not supported on filesystem at /home/golden/testy
-----------------------------------------------------------------
Detected abilities for source (read only) file system:
  Access control lists                         Off
  Extended attributes                          Off
  Mac OS X style resource forks                Off
  Mac OS X Finder information                  Off
-----------------------------------------------------------------
Making directory /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/foo
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/foo
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/hardlinked_file1
Hard linking /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/hardlinked_file2 to /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/hardlinked_file1
Unable to import module xattr.
Extended attributes not supported on filesystem at /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0
Unable to import module posix1e from pylibacl package.
ACLs not supported on filesystem at /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/dir_inc_check
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/dir_inc_check
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/regfile
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/regfile
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/5-_ a.
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/5-_ a.
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/A
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/A
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/:
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/:
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0
Removing directory /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0
-----------------------------------------------------------------
Detected abilities for destination (read/write) file system:
  Characters needing quoting                   ''
  Ownership changing                           On
  Hard linking                                 On
  fsync() directories                          On
  Directory inc permissions                    On
  Access control lists                         Off
  Extended attributes                          Off
  Mac OS X style resource forks                Off
  Mac OS X Finder information                  Off
-----------------------------------------------------------------
Writing mirror marker /tmp/home-backup/rdiff-backup-data/current_mirror.2005-10-14T08:15:34-05:00.data
Starting increment operation /home/golden/testy to /tmp/home-backup
Processing changed file .
Incrementing mirror file /tmp/home-backup
Touching /tmp/home-backup/rdiff-backup-data/increments.2005-10-14T08:14:51-05:00.dir
Copying inc attrs from () to /tmp/home-backup/rdiff-backup-data/increments.2005-10-14T08:14:51-05:00.dir
Setting time of /tmp/home-backup/rdiff-backup-data/increments.2005-10-14T08:14:51-05:00.dir to 1129261564
Getting signature of test.txt with blocksize 64
Getting delta of /home/golden/testy/test.txt with signature test.txt
Processing changed file test.txt
Writing file object to /tmp/home-backup/rdiff-backup.tmp.1
Segmentation fault
##################################################################

I'm starting to wonder.  I've had success with rdiff-backup on two other servers, but this one is a pain in the !ss.
Could it be making a difference that I'm running a AMD 64bit cpu?  I'm also running two sata drives as raid1 with the built in software raid.  Could that mean anything?

Dave Kempe wrote: Golden Butler wrote:

I'm still relatively a newbie to linux even though I've been using it
for almost two years, so excuse me for the ignorance. What is
"strace", and how would I be able to use to track down this segfault
problem?


strace follows a program and tracks down system calls etc. Its sometimes
useful, though generates a massive output for most things. If its
install simply doing 'strace command' will give you an idea.

Anyway, its probably not going to help you that much - its output is
pretty confusing.

can you try backing up to and from the same filesystem - ie try
rdiff-backup -v7 /home /tmp/home-backup

dave

Golden Butler wrote:
I'm still relatively a newbie to linux even though I've been using it
for almost two years, so excuse me for the ignorance. What is "strace",
and how would I be able to use to track down this segfault problem?

strace shows a program's syscalls -- roughly, the requests it's made to
the operating system. This will show you exactly what the program was
trying to do (so long it was something that it had to ask the OS for
help with -- like filesystem operations) at the point in time when it
crashed.

Let me echo something that's already been expressed: Since rdiff-backup
is written in Python, it itself is not going to segfault. What you're
seeing is some lower-level component going boom -- and strace should
show you what's going on.

If it isn't enlightening at first, consider telling it to follow forks
and setting a decently large string buffer length. Tell it to output to
file rather than screen -- the output is *long*, and just writing it all
to screen will slow things down substantially. If you can't read the
output, consider posting *the bits at the end, before the segfault* to
the list or putting the full trace up, compressed with bzip2, on a
website and posting the URL.

Hi,

Just a quick note...

On Fri, 14 Oct 2005, Golden Butler wrote:

Getting signature of test.txt with blocksize 64
Getting delta of /home/golden/testy/test.txt with signature test.txt
Processing changed file test.txt
Writing file object to /tmp/home-backup/rdiff-backup.tmp.1
Segmentation fault

IIRC, when running in less verbose mode, after 'Processing changed file
XXX' there's a line 'Incrementing file /backuptree-prefix/XXX'.

I'm not certain whether this incrementing is done from within the python
program, or if the python program calls the external rdiff program.

Do you have an rdiff binary on your system?


Regards,
Maarten

I'm not sure by what you mean rdiff binary?
-----Original Message-----
From: Maarten Bezemer <mcbrdiff < at > robuust.nl>
Date: Fri, 14 Oct 2005 15:52:19
To:Golden Butler <golden < at > cnt.org>
Cc:Dave Kempe <dave < at > solutionsfirst.com.au>, rdiff-backup-users < at > nongnu.org
Subject: Re: [rdiff-backup-users] RDIFF-F!CKUP (Very frusttrated)

Hi,

Just a quick note...

On Fri, 14 Oct 2005, Golden Butler wrote:

Getting signature of test.txt with blocksize 64
Getting delta of /home/golden/testy/test.txt with signature test.txt
Processing changed file test.txt
Writing file object to /tmp/home-backup/rdiff-backup.tmp.1
Segmentation fault

IIRC, when running in less verbose mode, after 'Processing changed file
XXX' there's a line 'Incrementing file /backuptree-prefix/XXX'.

I'm not certain whether this incrementing is done from within the python
program, or if the python program calls the external rdiff program.

Do you have an rdiff binary on your system?


Regards,
Maarten

Golden Butler wrote:
Okay, I'm almost ready to give up on rdiff-backup!

I hope you get your problem resolved - as others have already said, it
doesn't look like an rdiff-backup problem anyway.

More to the point, if you need help in future, I hope you're able to
pick a less rude subject. I'd remind you that you are talking about
software provided completely free, and largely the work of one
individual. Just because it doesn't work for you does not give you right
to be insulting.

Best regards,
Keith

Keith and others,

I by no means was insulting rdiff-backup or it's author. I'm very fond of rdiff-backup, I'm just frustrated right now because my job might be on the line if I don't get this resolved. Once again, I didn't mean to ruffle any feathers of this mailing list.

- Delamatrix
-----Original Message-----
From: Keith Edmunds <keith < at > midnighthax.com>
Date: Fri, 14 Oct 2005 17:30:31
To:Golden Butler <golden < at > cnt.org>
Cc:rdiff-backup-users < at > nongnu.org
Subject: Re: [rdiff-backup-users] RDIFF-F!CKUP (Very frusttrated)

Golden Butler wrote:
Okay, I'm almost ready to give up on rdiff-backup!

I hope you get your problem resolved - as others have already said, it
doesn't look like an rdiff-backup problem anyway.

More to the point, if you need help in future, I hope you're able to
pick a less rude subject. I'd remind you that you are talking about
software provided completely free, and largely the work of one
individual. Just because it doesn't work for you does not give you right
to be insulting.

Best regards,
Keith

this may be a shot in the dark, but have you tried installing the python
modules for extended attributes and access control lists?

google searches for "Unable to import module xattr" and "Unable to
import module posix1e from pylibacl package" both turned up this thread:

http://lists.gnu.org/archive/html/rdiff-backup-users/2005-07/msg00023.html

may not be at all related, but it would be nice to rule out some simple
filesystem/os quirkiness.

Golden Butler wrote:
I just tried backing up to and from the same filesystem with the the
same result, below:

#######################################################
Unable to import module xattr.
Extended attributes not supported on filesystem at /home/golden/testy
Unable to import module posix1e from pylibacl package.
ACLs not supported on filesystem at /home/golden/testy
-----------------------------------------------------------------
Detected abilities for source (read only) file system:
Access control lists Off
Extended attributes Off
Mac OS X style resource forks Off
Mac OS X Finder information Off
-----------------------------------------------------------------
Making directory /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/foo
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/foo
Touching
/tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/hardlinked_file1
Hard linking
/tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/hardlinked_file2
to /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/hardlinked_file1
Unable to import module xattr.
Extended attributes not supported on filesystem at
/tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0
Unable to import module posix1e from pylibacl package.
ACLs not supported on filesystem at
/tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/dir_inc_check
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/dir_inc_check
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/regfile
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/regfile
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/5-_ a.
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/5-_ a.
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/A
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/A
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/:
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/:
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/\
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/\
Touching /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0/
Deleting /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0
Removing directory /tmp/home-backup/rdiff-backup-data/rdiff-backup.tmp.0
-----------------------------------------------------------------
Detected abilities for destination (read/write) file system:
Characters needing quoting ''
Ownership changing On
Hard linking On
fsync() directories On
Directory inc permissions On
Access control lists Off
Extended attributes Off
Mac OS X style resource forks Off
Mac OS X Finder information Off
-----------------------------------------------------------------
Writing mirror marker
/tmp/home-backup/rdiff-backup-data/current_mirror.2005-10-14T08:15:34-05:00.data
Starting increment operation /home/golden/testy to /tmp/home-backup
Processing changed file .
Incrementing mirror file /tmp/home-backup
Touching
/tmp/home-backup/rdiff-backup-data/increments.2005-10-14T08:14:51-05:00.dir
Copying inc attrs from () to
/tmp/home-backup/rdiff-backup-data/increments.2005-10-14T08:14:51-05:00.dir
Setting time of
/tmp/home-backup/rdiff-backup-data/increments.2005-10-14T08:14:51-05:00.dir
to 1129261564
Getting signature of test.txt with blocksize 64
Getting delta of /home/golden/testy/test.txt with signature test.txt
Processing changed file test.txt
Writing file object to /tmp/home-backup/rdiff-backup.tmp.1
Segmentation fault
##################################################################

I'm starting to wonder. I've had success with rdiff-backup on two other
servers, but this one is a pain in the !ss.
Could it be making a difference that I'm running a AMD 64bit cpu? I'm
also running two sata drives as raid1 with the built in software raid.
Could that mean anything?

Dave Kempe wrote:

Golden Butler wrote:



I'm still relatively a newbie to linux even though I've been using it
for almost two years, so excuse me for the ignorance. What is
"strace", and how would I be able to use to track down this segfault
problem?




strace follows a program and tracks down system calls etc. Its sometimes
useful, though generates a massive output for most things. If its
install simply doing 'strace command' will give you an idea.

Anyway, its probably not going to help you that much - its output is
pretty confusing.

can you try backing up to and from the same filesystem - ie try
rdiff-backup -v7 /home /tmp/home-backup

dave



------------------------------------------------------------------------

_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki