Displaying 20 results from an estimated 13000 matches similar to: "--link-dest non-optimal without --owner (or when not root)"
2003 Mar 20
2
--link-dest uid/gid checking bug?
Hi --
I was very keen to download rsync and give it a whirl with the
new --link-dest feature. However, I was terribly puzzled when I
couldn't seem to get it working, even though --compare-dest with
the same argument would work. It seemed like new files would
be transferred even though files existed in the compare-dest/link-dest
location; compare-dest would detect them but link-dest would
2004 Mar 05
2
Problem with --link-dest when syncing AIX to Linux
Hello,
i'm using rsync 2.6.0 for daily-syncing some remote AIX 5.2 machine to a
local linux (RH 7.3) with using the --link-dest option for saving space
on incremental backups.
Even if there are no changes on the AIX machine, all files are newly
transferred on every new sync.
My test scenario (actisi=remote aix machine, actisa=local linux machine):
=====> Initial rsync
[mma@actisa
2003 Nov 05
1
--link-dest
Why does --link-dest assume -ugp ?
This patch removes those assumptions allowing mortal users to use
--link-dest for back ups. (I think... I didn't look at the large
picture.)
Joe
*** generator.c Thu Aug 29 09:44:55 2002
--- ../generator.c Tue Nov 4 09:12:59 2003
***************
*** 42,47 ****
--- 42,50 ----
extern int modify_window;
extern char *compare_dest;
extern int
2003 Apr 08
1
link_dest checks perms despite no -p -o or -g
When using --link-dest, this block of code in skip_file causes
new copies of files to be created if source and destination file
permissions differ, even if -p -o and -g haven't been specified.
if (link_dest) {
if((st->st_mode & ~_S_IFMT) != (file->mode & ~_S_IFMT)) {
return 0;
}
if (st->st_uid != file->uid || st->st_gid != file->gid) {
return 0;
}
}
2003 Apr 26
1
when does --link-dest create a link?
Hello,
(I found a post in the archives titled "link_dest checks perms despite
no -p -o or -g" on April 7th, which might be related - not sure...)
I'm trying to get a rotating daily backup going with previous days kept
as hard links to save on network transfer and disk space. The plan: on
day N, rsync to blah/N/, using --link-dest=../<N-1> (modulo 7 or
whatever).
My test
2003 Oct 22
1
rsync --dry-run --link-dest problem
I am trying to use rsync for making snapshots, sharing hardlinks at
the destination using the --link-dest option. In conjunction with
this, I would like for --dry-run to report some reliable-ish number
for how much space it is going to consume at the destination so that I
can arrange to free such space prior the launching rsync "for effect".
Right now, that isn't working:
#
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
2003 Oct 28
1
can't manage to get --link-dest working.
Hi,
I can't manage to get rsync's --link-dest option working.
Here is a step by step script which doesn't produce the good results.
# create test dir
mkdir testrsync
cd testrsync
mkdir orig
echo "abcd" > orig/testfile
# create a mirror
rsync -apog orig/ mirror/
# create another mirror using link-dest
rsync -apog --link-dest=mirror/ orig/ mirror2/
# look at inodes
ls
2003 Sep 27
1
Option --link-dest creates unexplained subdirectory
The following backup script works fine for test cases but for
doing a backup of 750 MB, the directory daily.1 has
a subdirectory daily.0, that is, there is
daily.1/daily.0
daily.2/daily.1
daily.3/daily.2
The directory daily.0 has nothing strange, no unusual links
at the top level neither hard or soft.
Also, the original directory has not unusual links.
All directories are in the same
2003 Jun 24
0
doc for --compare-dest could be clearer
On Mon, Jun 23, 2003 at 11:12:03PM -0400, Stephen Gildea wrote:
> I have a suggestion for how to make the documentation of rsync's
> "--compare-dest" option clearer.
>
> Maybe it would be clearer if I had some problem this option would solve,
> but as it is, I couldn't figure it out from the manual. The description
> in the rsync 2.5.6 manual page starts:
2003 Nov 26
1
rsync - some issues - as super user & option --owner
Hi,
rsync version 2.5.6 protocol 26.....used in mdk 9.2
I have some difficulties..
As user internet...in console..
command...
su -c "rsync -auvr /home/internet/tstrsync1/ /mnt/win_d/tstmdk1/ 1>
auvr-su.txt 2> auvr-su.err"
results.....
auvr-su.txt...
building file list ... done
<<snip>>
use-update
wrote 1179 bytes read 132 bytes 2622.00 bytes/sec
total size is 672
2002 Mar 22
1
[PATCH] --link-dest option
Please CC me. I'm not subscribed.
Attached is a patch against 2.5.4pre1 CVS current to add the
--link-dest option so rsync will create hardlinks for
unchanged regular files to a directory on the destination.
This is like --compare-dest except that the result is not a
sparse tree.
Also included is extension to --(ex|in)clude-from to allow -
for stdin.
Could one of the maintainers please add
2002 Aug 02
1
[patch] --link-dest
Updated to current cvs without the --exclude-from - patch.
This patch allows specifying a --link-dest path similar to
--compare-dest except that unchanged files are hard-linked to the
--link-dest path instead of producing a sparse tree.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember
2003 Mar 15
1
Dirvish, --link-dest and permissions
(I'm not sending this to dirvish@pegasus because I think that this message
applies more to rsync's --link-dest option than to just dirvish.)
I recently noticed a huge spike in dirvish network usage and traced it to
files whose permissions had been changed. (with rsync v2.5.6)
I understand and agree that a --link-dest copy of a source file cannot be
hardlinked to, but couldn't a
2003 Dec 30
1
rsync 2.5.7 link-dest seems broken
Hi --
I'm experiencing problems when using rsync between two different machines.
Details follows:
Both machines are running 2.4.23, rsync versions on both are identically
configured versions of 2.5.7:
rsync version 2.5.7 protocol version 26
Copyright (C) 1996-2002 by Andrew Tridgell and others
<http://rsync.samba.org/>
Capabilities: 64-bit files, socketpairs, hard links, symlinks,
2017 May 26
9
[Bug 12806] New: Deleting in a row of hardlinked snapshots resets file permissions.
https://bugzilla.samba.org/show_bug.cgi?id=12806
Bug ID: 12806
Summary: Deleting in a row of hardlinked snapshots resets file
permissions.
Product: rsync
Version: 3.1.0
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: core
2002 Mar 08
1
[PATCH][RFC] space saving incrementals
Please CC me directly as i'm not on the list.
I have attached a patch against latest CVS (cvs diff -u)
that adds the following functionality. I can break it up if
you would prefer it in pieces. Comments welcome.
o add compare-perms option
This creates a new inode for a file even if only
the perms have changed. This way if a file
outside of destdir is hardlinked to a dentry
inside
2008 Jan 20
1
--link-dest vs. special files and owner/group changes
rsync 2.6.9 --link-dest does
- not hardlink special files (symlink, device nodes)
This doesn't take much space, but it clutters the logfiles
- change owner/groupship on the hardlink
So if I use a hard-linked-tree-per-day, it changes history also
Is this still the same with newer versions?
Are there options to modify this behavior?
If not, why not? :-)
louis
--
GMX FreeMail: 1 GB
2004 Jan 26
1
patch for linux capabilities
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)
2003 Aug 26
3
Rsync hangs with protocol incompatibility issues
hi guys
Environment
2 servers (SunOS 5.8)
rsync 2.5.6
Problem
For a disaster recovery solution, we are running trying to synchornize interwoven backup stores between these 2 environments (server A and server B)
The rsync operation is initiated over the network using 'rsh'. Once initiated from server A the rsync operation freezes with no indication. When the debug flag is enabled we get