On Wed, Jun 29, 2011 at 1:25 AM, Michael Hierweck
wrote:
> rsync: failed to write xattr user.rsync.%stat for "path/to/a/socket" (in
> backup): Operation not permitted (1)
>
The --fake-super option turns devices and special files into normal files
with an xattr attribute with the real file mode an
nvbolh...@aimvalley.nl wrote:
I'm using rsync on an embedded powerpc platform
with flash filesystem.
Because of a power-cycle a local file got corrupted.
This file is /flashfs/isd1, it has the correct size but
wrong MD5SUM (cd5...).
Using rsync to retrieve the right file (from a remote machine)
Bump.
I have still not found a solution for this. Do you have any ideas on
how to debug it?
Thanks.
Med venlig hilsen/Kind regards
Thomas Damgaard Nielsen
http://thomasdamgaard.dk
On Tue, Apr 28, 2009 at 2:35 PM, Thomas Damgaard wrote:
> Hi
>
> I use rsync for daily backups from a mailserver.
On Wed, Mar 19, 2008 at 10:11:52AM -0700, rdwyer wrote:
> Is there a way to absolutely prevent rsync from copying
> a specific file in a directory where every file but that one is to be
> copied?
One thing you can do to prevent a particular file from being transferred
is to give rsync an absolute-
On Wed, 2008-03-19 at 10:11 -0700, rdwyer wrote:
> Rsync seems to intermittently ignore the exclude statement and copies them
> from time to time.
> rsync -avz --delete --update --stats
> --exclude=/library/webserver/documents/domains/mydomain/file_to_exclude.html
> -e ssh [EMAIL PROTECTED]:/Web_F
On 5/9/07, Paul Slootman <[EMAIL PROTECTED]> wrote:
On Tue 08 May 2007, Wayne Davison wrote:
>
> You can read the very latest manpage with my improvements here:
>
> http://rsync.samba.org/ftp/rsync/nightly/rsync.html
>
> E.g., there's extra quick-check discussion in the DESCRIPTION section.
Yes,
On Tue 08 May 2007, Wayne Davison wrote:
>
> You can read the very latest manpage with my improvements here:
>
> http://rsync.samba.org/ftp/rsync/nightly/rsync.html
>
> E.g., there's extra quick-check discussion in the DESCRIPTION section.
Yes, that's a great improvement. This is typically one
On Tue, May 08, 2007 at 09:49:05AM -0700, Wayne Davison wrote:
> The summary description could use an extra mention, though.
You can read the very latest manpage with my improvements here:
http://rsync.samba.org/ftp/rsync/nightly/rsync.html
E.g., there's extra quick-check discussion in the DESCR
On Tue, May 08, 2007 at 03:45:40PM +0300, Atte Peltomaki wrote:
> Forgets to say that "efficient checksum-search algorithm" is not enabled
> by default *doh*.
Untrue. The checksum-search algorithm is enabled, just the pre-transfer
checksum check is not. Those are two different things.
The "qui
You need to supply the --checksum option if you want to make sure
that the contents are indeed identical. This is normally not done
as that would cause a massive IO load; cases that size and
timestamp are identical but not the contents don't usually
happen...
The manual is indeed not very clear
On Tue, May 08, 2007 at 01:07:51PM +0200, Paul Slootman wrote:
> On Tue 08 May 2007, Atte Peltomaki wrote:
> > Source:
> >
> > md5sum:
> > 2ac4a4ad88da17f49d26c9e578ce5432 somefile.exe
> > sha1sum:
> > eaabb30b716e993be000b89208e2d9f63e78f052 somefile.exe
> > ls -l:
> > -rwxrw 1 user group
On Tue 08 May 2007, Atte Peltomaki wrote:
>
> I'm seeing a weird problem with rsync 2.6.9 protocol version 29 on
> Debian Sarge. When copying a file from one location to another between
> two Debian boxes, if destination includes a file with same size and
> name, rsync fails to see that they are n
Yes, I even made the rsync server user a local
administrator for a test, as well as created a share for the directory and gave
the user permission for it, as well as file permissions on the
directory...
C.
- Original Message -
From:
Srinivasa
Battula
To: rsync@lists.s
he DOS 8.3
filenames.
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of
Corey Wirun - personalSent: Sunday, June 25, 2006 12:40
PMTo: rsync@lists.samba.orgSubject: Re: Rsync fails to
rename on Windoze2003
Hi Tony,
I understood. I though
, June 25, 2006 12:40
PMTo: rsync@lists.samba.orgSubject: Re: Rsync fails to
rename on Windoze2003
Hi Tony,
I understood. I thought you were
referring to possible confusion between two files on the source - like
RICHED~2.cab and RICHED~1.cab getting copied to the target and the
Original Message -
From:
Tony
Abernethy
To: Corey Wirun - personal ; rsync@lists.samba.org
Sent: Sunday, 25 June, 2006 10:17
Subject: RE: Rsync fails to rename on
Windoze2003
TARGET
The
rename is on the target side, not the source.
If
the file is OPEN on the targ
, June 25, 2006 10:16
AMTo: rsync@lists.samba.orgSubject: Re: Rsync fails to
rename on Windoze2003
Thanks Tony,
The source only has one file: RICHED~1.cab,
so my guess is that the short name business isn't what is biting me
here.
Corey.
- Original Me
07:31
Subject: RE: Rsync fails to rename on
Windoze2003
This
is mostly wild guesses (with luck you get some more knowledgeable
answers)
From
what I have observed ...
file
of the form .RICHED~1.cab.IEKJmo is an rsync temporary of file
RICHED~1.CAB
Trying to renam
PMTo: rsync@lists.samba.orgSubject: Re: Rsync fails to
rename on Windoze2003
Some further information:
I went back to 2.6.6 of rsync on the client and
server and at least the entire sync completes. I still get the
'Permission Denied' problem on the rename though. I
Some further information:
I went back to 2.6.6 of rsync on the client and
server and at least the entire sync completes. I still get the 'Permission
Denied' problem on the rename though. I had a look at the logs and it appears the rename error is _always_
on a file name with a '.' as the
On Wed, May 17, 2006 at 05:03:15PM -0700, Ferguson, Eric wrote:
> rsync --whole-file --temp-dir /tmp file.txt
> destination.machine:/path/to/file/file.txt
>
> error:
>
> rsync: stat "/path/to/file/file.txt" failed: No such file or directory (2)
> rsync error: some files could not be transferred
On Tue, Sep 28, 2004 at 03:57:06PM +0200, Max Gilead wrote:
> rsync -v --recursive --rsh="ssh" [EMAIL PROTECTED]:* dest_dir
> receiving file list ... link_stat "/home/login/*" failed: No such file
> or directory
This isn't an rsync problem, this is a shell-induced problem due to you
using a wildc
>I often post them to the mailing list, but the best place to find fixes
>is in the CVS version. (This fix has been in CVS since early May, for
>instance.) See the "NEWS" file from CVS for a good summary of what has
>changed.
Ok. Many thanks again!
Bye, Andy
--
Andreas Ley, Rechenzentrum, Uni
On Tue, May 18, 2004 at 10:26:23AM +0200, Andreas Ley wrote:
> Bingo! This patch indeed fixes the problem. Is this an 'official' patch and
> is there an 'official' place to look for patches to released versions?
I often post them to the mailing list, but the best place to find fixes
is in the CVS
>http://lists.samba.org/archive/rsync/2004-May/009380.html
Bingo! This patch indeed fixes the problem. Is this an 'official' patch and
is there an 'official' place to look for patches to released versions?
Many thnx, Andy
--
Andreas Ley, Rechenzentrum, Universitaet Karlsruhe, D-76128 Karlsruhe,
On Mon, May 17, 2004 at 09:22:14AM -0700, Wayne Davison wrote:
> On Mon, May 17, 2004 at 04:45:21PM +0200, Andreas Ley wrote:
> > #0 0x400a46d9 in strncmp () from /lib/libc.so.6
>
> That looks like the segfault I fixed [that affected] 2.6.1.
No, that's not right. I'm mis-remembering when that c
Andreas Ley wrote:
I haven't been able to duplicate the crash you two are seeing, so if
either of you can send me a backtrace of the crash (either from a core
dump or by doing some creative gdb attaching), I'd appreciate it.
I didn't get a core, but suceeded tu run gdbserver:
#0 0x400a46d9 in str
On Mon, May 17, 2004 at 04:45:21PM +0200, Andreas Ley wrote:
> #0 0x400a46d9 in strncmp () from /lib/libc.so.6
That looks like the segfault I fixed in 2.6.1. I looked back at your
original message, and it looks like I misread ">= 2.6.1" as "> 2.6.1".
If you're using 2.6.1, please upgrade to 2.6.
>I haven't been able to duplicate the crash you two are seeing, so if
>either of you can send me a backtrace of the crash (either from a core
>dump or by doing some creative gdb attaching), I'd appreciate it.
I didn't get a core, but suceeded tu run gdbserver:
#0 0x400a46d9 in strncmp () from /l
On Fri, May 14, 2004 at 04:56:47PM +0200, Andreas Ley wrote:
> I get a SEGFAULT.
I haven't been able to duplicate the crash you two are seeing, so if
either of you can send me a backtrace of the crash (either from a core
dump or by doing some creative gdb attaching), I'd appreciate it.
..wayne..
Andreas Ley wrote:
The two machines are Debian stable with kernel 2.4.26.
I'm running rsync even on a single box, or through ssh between 2 boxes.
Both are linux-2.6.6.
Hope this helps finding the bug. Can I provide more information or run more
tests?
we are on the same bug ! that's sure.
--
Bapt
Hi!
I seem to have a similar problem. I checked different versions and options,
and it seems to happen when the server version is >= 2.6.1 - there's no
problem with 2.6.0. The client version doesn't matter. The --delete option
is required to show the bug. The two directories may well be uptodate a
PROTECTED]@[EMAIL PROTECTED] on 05/17/2001 05:24:04 PM
Sent by:[EMAIL PROTECTED]
To: [EMAIL PROTECTED]@SMTP
[EMAIL PROTECTED]@SMTP
cc:
Subject: Re: rsync fails
Classification:
I just got done dealing with this problem.
It was solved for me using the
--rsync-path=/usr/local
:[EMAIL PROTECTED]]
Sent: Friday, 18 May 2001 11:09
To: [EMAIL PROTECTED]; Bob Foster
Subject: Re: rsync fails
I just got done dealing with this problem.
It was solved for me using the
--rsync-path=/usr/local/bin/rsync
flag, specifying the remote location of rsync.
It be great if someone knew how
I just got done dealing with this problem.
It was solved for me using the
--rsync-path=/usr/local/bin/rsync
flag, specifying the remote location of rsync.
It be great if someone knew how to avoid using
this parameter.
cheers,
Dave
- Original Message -
From: "Bob Foster" <[EMAIL PROT
35 matches
Mail list logo
