Displaying 20 results from an estimated 9000 matches similar to: "[Bug 13656] New: --link-dest target with symbolic links from different user produces unnecessary error"
2004 Jan 26
1
--link-dest not working with rsync daemon?
I am puzzled as to why I can't get the option --link-dest to work
properly. When I use this option when both source and destinations are
on a local filesystem the hard-linking of the target against the
link-dest directory does work, but when the source is a remote directory
(via ssh or rsync server) hard links are not created. I suspect it has
something to do with setting the correct
2010 Jul 16
4
--compare-dest weirdness
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
2010 May 12
3
DO NOT REPLY [Bug 7424] New: -x with sshfs
https://bugzilla.samba.org/show_bug.cgi?id=7424
Summary: -x with sshfs
Product: rsync
Version: 3.0.7
Platform: x64
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P3
Component: core
AssignedTo: wayned at samba.org
ReportedBy: bugs at dotcommie.net
QAContact: rsync-qa at
2004 Mar 12
0
Two bugs in rsync (--dry-run and --delete-excluded)
Hi rsync gurus!
[Please Cc: me, as I am NOT subscribed to the list!]
First the data points:
debian/woody, local server=i386 arch, remote is alpha arch
rsync version on both debian 2.5.5-0.2
While upgrading our server to a raid we were hit by a bug which I really
consider very strange:
The option -n/--dry-run does NOT change files, but DELETE files when
called with --delete.
Test case I had:
$
2014 May 27
1
[Bug 10637] New: rsync --link-dest should break hard links when encountering "Too many links"
https://bugzilla.samba.org/show_bug.cgi?id=10637
Summary: rsync --link-dest should break hard links when
encountering "Too many links"
Product: rsync
Version: 3.0.9
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
Component: core
AssignedTo:
2001 Oct 12
1
Confused by modules
Hi,
I'm confused as to the purpose of rsync modules. I know how to set them up
in rsyncd.conf, and can list the available modules on a remote linux machine
using 'rsync camlinux01::' from a Win32 client, but I can't find any
information on what they are actually for.
The man page for rsyncd.conf talks about them as if they are vitaly
important, but the man page for rsync
2012 Apr 15
0
Bug#666024: rsync --link-dest can incorrectly hardlink together destination files
[please Cc: 666024-forwarded at bugs.debian.org on any replies, thanks]
Please see the attached Debian bug report, which includes a helpful
bug-reproducing shell script; I've confirmed this still happens with
3.0.9.
Paul Slootman
On Tue 27 Mar 2012, Ian Jackson wrote:
> Package: rsync
> Version: 3.0.7-2
>
> With rsync --link-dest, if two different source files (not hardlinked
2003 May 09
1
Bug report: deletion of files only on remote system is not logged.
I was told that my earlier submission of this report contained a
user-hostile attachment (courtesy of Outlook), so here it is again, with
the log included below.
The problem: Files that exist only on the remote system are deleted
silently (i.e. not logged), rather than noisily as implied by the
recommendation of --dry-run in the rsync man page definition of --delete
to see what would be
2007 Jul 30
2
DO NOT REPLY [Bug 4834] New: --inplace with --backup --backup-dir does not work
https://bugzilla.samba.org/show_bug.cgi?id=4834
Summary: --inplace with --backup --backup-dir does not work
Product: rsync
Version: 2.6.9
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy: joost@seat-ibiza.nl
2005 Jan 16
1
Rsync through SSH can't find directory
Up until recently, I was running a standard rsync/rsh to rsyncd server
combination to sync files. Due to security concerns, I'd like to switch to
rsync through ssh.
I'm testing with the following from the client side:
rsync --verbose --progress --stats --compress --rsh="/usr/local/bin/ssh -p
XXXX" \
--recursive --times --perms --copy-links --delete \
/rsynctest/test1
2007 Jan 23
1
--link-dest copying modified files
Hi!
It's me again with another --link-dest issue:
I am using dirvish (www.dirvish.org) to create daily backup on disk
images.
dirvish is using rsync with --link-dest pointing to the last good image.
This creates images with hardlinks to unmodified files. So far so good.
Now I want to create a "current" filetree with hardlinks pointing to the
last image.
rsync -vaH --delete
2010 Jan 22
1
Still stuck with exculsion text file pattern
I would like to rsync the dirs "Documents" "Sofware" and the .evolution
files only. and remove the *~ files
----------------------------------------------
Command:
#rsync -r -n -t -v --progress
--exclude-from=r2 /home/mt/ /home/mt/rsyncTest/
------------------------------------------
#text file <r1>:
+ .evolution/calendar/local/system/calendar.ics
+
2005 Jan 19
1
PROPOSAL: --link-hash-dest, additional linking of files to their HASH values
I'm using a few utilities to accomplish the same thing in a second pass
after rsync runs. The utils all use a two-layer hash (256 directories of
256 subdirectories), which with our current backups puts a little over 100
files per directory. Anywhere from hundreds of thousands to tens of
millions of files shouldn't waste too many inodes or put a gross number of
files into each directory.
2010 Dec 14
7
DO NOT REPLY [Bug 7865] New: files or dirs with more than 16 ACLs are not rsynced correctly
https://bugzilla.samba.org/show_bug.cgi?id=7865
Summary: files or dirs with more than 16 ACLs are not rsynced
correctly
Product: rsync
Version: 3.0.7
Platform: IA64
OS/Version: HP-UX
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned at samba.org
2005 Aug 02
0
[Bug 2947] New: stdout with [-v] -H --link-dest and slink/sock/fifo/regf
https://bugzilla.samba.org/show_bug.cgi?id=2947
Summary: stdout with [-v] -H --link-dest and slink/sock/fifo/regf
Product: rsync
Version: 2.6.5
Platform: All
OS/Version: FreeBSD
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy:
2011 May 11
7
[Bug 8130] New: ACL and link-dest do not work together
https://bugzilla.samba.org/show_bug.cgi?id=8130
Summary: ACL and link-dest do not work together
Product: rsync
Version: 3.0.8
Platform: All
OS/Version: All
Status: NEW
Severity: major
Priority: P5
Component: core
AssignedTo: wayned at samba.org
ReportedBy: az9901 at gmail.com
2003 Dec 20
1
why not link devices with --link-dest option?
I notice that devices are not hardlinked when using the --link-dest
option, for instance:
rsync -aH --link-dest=../bar/ foo/ baz/
When foo/zero is a device, baz/zero is not a hardlink to bar/zero. How
come?
$ rsync --version
rsync version 2.5.6 protocol version 26
on linux 2.4.x
--
Russell Senior ``I have nine fingers; you have ten.''
seniorr@aracnet.com
2004 Apr 07
2
--suffix problem - possibly bug?
I'm having an issue with the --suffix and -b flags -
I've tried the following commands:
rsync -avbr --backup-dir=/rsyncbackup rsynctest user@server.com::module
rsync -avbr --backup-dir=/rsyncbackup --suffix="" rsynctest
user@server.com::module
and either way, I wind up with a tilde as a suffix on all the files
moved into the backup directory at time of synchronization.
2013 Dec 19
5
[Bug 10334] New: rsync doesn't log hardlink-copies using --link-dest
https://bugzilla.samba.org/show_bug.cgi?id=10334
Summary: rsync doesn't log hardlink-copies using --link-dest
Product: rsync
Version: 3.0.9
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: core
AssignedTo: wayned at samba.org
ReportedBy: Kontakt at
2003 Sep 28
1
bug (filelist) for platforms solaris and darwin (macosx) and *not* linuxi386
I have found a nasty bug when a file, which is in some of many sources,
shall be copied to a target.
The linux-Version works well but rsync 2.5.{2|5|6} under solaris9 (gcc
2.95.3) and darwin (gcc 3.1) do not. The decision which file (out of which
src) shall be copied depends on the number of src dirs given on the command
line.
This bug bytes us very hard, because we decided to rely on rsync