similar to: rsync not reporting diskfull error

I'm using rsync 3.0.7 on Mac OS X 10.6, compiled according to Mike Bombich's instructions at http://www.bombich.com/rsync.html. Rsync repeatedly exits with a protocol data stream error when trying to copy some com.apple.FinderInfo extended attributes. While testing this issue, I found that rsync is not actually copying all extended attributes even when there is no error message. I'm

Typically rsync exits and reports an error such as: rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync: write failed on "/Volumes/Backup/big_file.dmg": No space left on device (28) rsync: connection unexpectedly closed (67174 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at /src/ rsync-3.0.5/io.c(600)

I am a developer on the LBackup project. An LBackup user recently posted a question to the mailing list asking about the following error. > "rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0)" Link to thread : <http://www.mail-archive.com/lbackup-discussion at lists.connect.homeunix.com/msg00040.html> My understanding of this error is that when copying files via

How do you handle snapshotting? or do you leave that to the block/fs virtualization layer? /kc On Fri, Apr 17, 2015 at 01:35:27PM +1200, Henri Shustak said: >> Our backup procudures have provision for looking back at previous directories, but there is not much to be gained with recycled directories. Without recycling, and after a failure, the latest available backup may not have much

rsync folks, Henri Shustak <henri.shustak at gmail.com> wrote: > LBackup always starts a new backup snapshot with an empty directory. I > have been looking at extending --link-dest options to scan beyond just > the previous successful backup to (failed backups / older backups). > However, there are all kinds of edge cases which are worth considering > with such a changes. At

Hi, As the man page says, the --partial flag is to "keep partially transferred files". I'm assuming if I don't have partial flag any partially transferred files should be deleted. However this is not what I'm seeing. Example: (Using a big file so that rsync times a while to run. This gives me time to hit CTRL-C for the SIGINT). > mkdir example > dd if=/dev/zero

As Ben mentioned, ZFS snapshots is one possible approach. Another approach is to have a faster storage system. I have seen considerable speed improvements with rsync on similar data sets by say upgrading the storage sub system. -------------------------------------------------------------------- This email is protected by LBackup, an open source backup solution http://www.lbackup.org

I am involved with the development of LBackup <http://www.lbackup.org> Recently there was a post to the lbackup-dicussion mailing list. <http://tinyurl.com/lbackup-discussion-device-not> Within the post they reported the following error: > rsync: read > "/Volumes/Drobo_HD/lbackups/theserver.Homes/Section.0/Faculty/andrewmac/.DS_Store": > Device not configured

Just chiming in slightly off topic. As a first step if you are going to be backing up files to some media with a computer it would be a really good idea to ensure, that the hardware being used is not faulty. I am not saying that your hardware is faulty. However, it would be worth checking this somehow. Check the drive media for bad blocks, check that all the cables are working well. Ensure the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/14/2015 11:35 PM, Henri Shustak wrote: >> Ill take a look but I imagine I cant backup the 80 Million files >> I need to in under the 5 hours i have for nightly >> maintenance/backups. Currently it's possible by recycling >> directories... I would expect that recycling directories actually makes this worse. With an

Hiya, I can see it's a regular subject on this list. I, like others wanted to use rsync to synchronise two block devices (as it happens one lvm volume and one nbd device served by qemu-img on a remote host from a qcow2 disk image so that I can keep the old versions) As I couldn't find any report of it being done successfully, I'm just sharing my findings as it might benefit others.

https://bugzilla.samba.org/show_bug.cgi?id=3653 Summary: Silence 'vanished files' messages Product: rsync Version: 2.6.8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: count-samba@flatline.de

I was wondering if it might be possible for an rsync developer to look over the attached patch (tested on Linux 2.4.24 against the rsync-2.6.0 release), and offer suggestions on how I could improve it. Basically I want to use Linux finer grained capabilities to retain only CAP_SYS_CHROOT & CAP_DAC_READ_SEARCH when rsync drops root privs. That way I can take whole system backups as a (mostly)

I'm really confused with all the examples out there and all different types of incremental backups. I tried several scripts but cannot reduce the size of my backup folders. What I want is to backup my documents to my external drive every month and save as much disk space as possible. Lets say I have 3 backup directories in the external drive, backup03.10, backup04.10 and backup05.10. I want

Hi All, I am writing a backup program for my computer. brief outline is as follows. Running ubuntu 10.04 2 main partitions, / and /home, both ext3. 1 external usb hdd, ext3, mounted to /backups/main. once every couple of days, rsync backs up, using following command, everything worth backing up in / and /home partitions to a folder /backups/main/Full. command: "rsync -vrhRupElog

Hi, I have few questions that could not find answers to in documentation. Different filesystems: Lets say I want to keep all extended attributes and everything else, so I use -A, -X, --perms etc., together with --fake-super. Now, lets say source FS supports some attributes not supported on target FS (for example, XFS extended attributes). Would this work as expected (ie. extended attributes are

Am 19.06.2016 um 19:27 schrieb Simon Hobson: > Dennis Steinkamp <dennis at lightandshadow.tv> wrote: > >> i tried to create a simple rsync script that should create daily backups from a ZFS storage and put them into a timestamp folder. >> After creating the initial full backup, the following backups should only contain "new data" and the rest will be referenced

Greetings, I posted this to a couple online forums already am am already doubting anyone will be able to directly help me solve my problems. So I am here to query the experts directly: > I have a number of rsync clients trying to connect to an rsync server > routinely, and they're intermittently failing with one of a couple error > messages. > > Either: > > 2010/09/15

> Our backup procudures have provision for looking back at previous directories, but there is not much to be gained with recycled directories. Without recycling, and after a failure, the latest available backup may not have much in it. Just wanted to point out that LBackup has a number of checks in place to detect failures during a backup. If this happens, then that backup is not labeled as a

is there anything special to do this from the daemon server. I've setup the /etc/rsyncd.conf with some filesystems and I would rather originate (control) my rsyncs from this server and not from the hosts that have the data I want. ie. I want to pull not push. for instance my rsyncd.conf [www] comment = www path = /snaps/www numeric ids = true log file = /snaps/rsync/logs/www.log pid file