See answers below:
On 29/01/2011, at 11:52 PM, henri wrote:
I've recently had problems with a backup job on a Mac OS X Server (10.6)
producing this error:
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]:
Broken pipe (32)
rsync: connection unexpectedly closed (3225054 bytes received so far)
[sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(601)
[sender=3.0.7]
Can anyone tell me what it means, why it would occur and most importantly
how to fix it.
In order to help answer your questions and provide relevant advice would you
kindly provide answers to the following questions :
(1) What is the largest file being backed up?
I do not know, but it could be up to 40GB.
(2) Approximately, what is total size of this particular
backup source?
The backup source is about 1TB but the excludes file reduces it down to fit on
a 500GB Backup drive.
(3) Is the backup taking place via SSH (network) or locally?
Backup is executed locally.
(4) If you are backing up via SSH, then please let me know if your rsync
binaries 32bit or 64bit. To find this information a running a command
which is similar to the following on both systems, should provide the
required information : /usr/local/bin/rsync_v3.0.7 --version
(5) Is the backup data being written to DAS, internal storage
or a network mount point?
The backup destination is a Tandberg Data RDX Drive. Effectively an external
hard drive.
(6) Is the backup destination on a virtual file system such as
a sparse bundle?
No.
(7) What is the disk utilization and free space of the destination
file system? On the system which is connected to the backup storage
device the following command will provide this information : df -hi
Filesystem SizeUsedAvail Capacity iused
ifree %iused Mounted on
/dev/disk3s2 465Gi465Gi 32Mi100%122003451
8191 100% /Volumes/Backup
(8) Would you kindly confirm whether the destination file systems is
formatted as HFS plus? In order to find this information, running the
following command on the system connected to the destination
should provide this information : diskutil list
(9) Have you attempted to perform a backup to a new destination file system
using rsync rather than lbackup?
Finally, would you please execute the backup (manually) via the terminal and
then provide the output from which is returned from lbackup to your shell.
If you would prefer to reply with any of this information off list, then
simply visit the following URL for Lucid contact details :
http://www.lucidsystems.org/contact/
Thank you.
As it turns out, the backup was running out of space for one reason or another.
Removing the previous backup and manually re-running the backup seams to have
cured the problem.
It would be nice if LBackup could report a friendlier error message in these
sort of events.
___
lbackup-discussion mailing list
http://www.lbackup.org
Change options or unsubscribe :
http://lbackup.org/mailing_lists
