There is a bug in librsync which is triggered by very large files =
4GB, I believe. Unfortunately, I did not think to include the patch in
the Windows build. I will make sure it is in the next release.
FWIW, I have definitely seen this problem every now and then
historically on hosts
On Oct 23, 2008, at 11:23 AM, dchiang wrote:
I seem to be running into some errors when trying to back up a
couple of outlook PST files. These files usually range from around 1
to 4 GB in size.
A couple of questions:
- Was Outlook open at the time of the backup?
- What version of Windows
- Was Outlook open at the time of the backup?
Nope, all files in the folder were mirrored from another network drive earlier.
- What version of Windows are you using?
Windows XP SP3
- What type of processor? (x64 or 32-bit)
32-bit
Thanks
On Oct 24, 2008, at 8:41 AM, dchiang wrote:
- Was Outlook open at the time of the backup?
Nope, all files in the folder were mirrored from another network
drive earlier.
What does that mean? mirrored ? What mechanism did you use to do
that?
Can you confirm the file size of the files
Andrew Ferguson wrote:
On Oct 24, 2008, at 8:41 AM, dchiang wrote:
- Was Outlook open at the time of the backup?
Nope, all files in the folder were mirrored from another network
drive earlier.
What does that mean? mirrored ? What mechanism did you use to do
that?
Can
On Oct 24, 2008, at 12:13 PM, Ryan How wrote:
I've been backing up 30GB+ files from windows to linux no
problems... but running 1.2.1. I'm waiting for 1.2.3 for long
filepaths :)
The bug is architecture-dependent, I believe. see:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355178
Hi all,
I seem to be running into some errors when trying to back up a couple of
outlook PST files. These files usually range from around 1 to 4 GB in size.
I've been using the windows version of the rdiff-backup 1.2.2, and I'm doing
the backup locally (from one internal drive to another).
Hello Group,
Sorry if this is an off-topic question for rdiff-backup. I had problem
installing librsync on a 64-bit server. My rdiff-backup process runs
smoothly on 32-bit workstation.
Here is the error during the installation:
gcc -Wall -Wshadow -Wundef -Wwrite-strings -Wmissing-prototypes -
RudySC wrote:
/usr/lib/libpopt.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
make[2]: *** [rdiff] Error 1
make[2]: Leaving directory `/usr/local/src/librsync-0.9.7'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
I already had the 64-bit libsrync. But I had a new problem installing
the rdiff app itself. Here's the error I encountered:
python setup.py install
running install
running build
running build_py
running build_ext
building 'rdiff_backup._librsync' extension
gcc -pthread -shared
RudySC wrote:
I already had the 64-bit libsrync. But I had a new problem installing
the rdiff app itself. Here's the error I encountered:
python setup.py install
running install
running build
running build_py
running build_ext
building 'rdiff_backup._librsync' extension
gcc -pthread
Hello,
Can somebody explain the following error to me:
python: ERROR: (rs_file_copy_cb) seek failed: Invalid argument
python: ERROR: (rs_job_complete) patch job failed: IO error
UpdateError home/ton/Samwise/Samwise_c_18082006.tib librsync error 100 while in
patch cycle
I suspect the file size
Hello,
Glad to see that rdiff-backup has reached version 1 :-)
After upgrading, I get the following error:
python: ERROR: (rs_file_copy_cb) seek failed: Invalid argument python:
ERROR: (rs_job_complete) patch job failed: IO error UpdateError
tmp/20050812/sp_trembl.dat librsync error 100 while
Troels Arvin wrote:
The files (sp_trembl.dat and sp_uni.dat) are rather large (3.6 and 4.2 GB)
but otherwise not special. Host receiving data is a CentOS 4.1 (~=RHEL
4.1) host; host sending data is a SuSE Professional 8.1 installation.
what version of librsync and python on those?
I thought
14 matches
Mail list logo
