Displaying 20 results from an estimated 2000 matches similar to: "Special Characters in Filenames -> rsync error code 24, files vanished"
2015 Nov 09
2
CentOS6: missing kernel module?
Testing out tipc for cluster development, and running into an immediate snag.
tipcutils was found in EPEL but despite having a "compatible" kernel, it
doesn't seem to actually work.
It's a completely updated system, Intel i5 with 16 GB of RAM, nothing
remarkable.
Any ideas?
[root at backup2 ~]# tipc-config -netid=1234 -a=1.1.1 -be=eth:eth0
TIPC module not installed
2007 Jul 06
1
Connection problem with 3.0.25a [solved]
I found a solution for this, but I don't understand why this made a
difference.
First, here's output from testparm:
----------------------------------------------------
testparm
Load smb config files from /usr/local/etc/smb.conf
Processing section "[backup2$]"
Processing section "[backup$]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a
2013 Mar 28
1
[Bug 9749] New: hardlinkes files are copies instat of make a link
https://bugzilla.samba.org/show_bug.cgi?id=9749
Summary: hardlinkes files are copies instat of make a link
Product: rsync
Version: 3.0.9
Platform: x86
OS/Version: Linux
Status: NEW
Severity: major
Priority: P3
Component: core
AssignedTo: wayned at samba.org
ReportedBy: dieter.ferdinand at
2008 Dec 19
1
24, file has vanished
Hi all!!
I copy files and directories from server with Windows 2000 Server to
server with Debian. The copy made with rsync, the instruction is the next:
rsync -av --iconv=WINDOWS-1252,utf-8 directory from windows 2000 server directory from Debian
There are the error:
file has vanished
What happenned?
thanks
--
Xavi Aranda
Equip T?cnic ? ASSOCIACI? PER A JOVES TEB
Carrer dels
2003 Jan 09
2
Help With Restoring
Hi All,
I have been using rsync to backup to a central server with a 7 day
incremental script on 2 Redhat boxen.
#!/bin/sh
PATH=/usr/local/bin:/usr/bin:/bin
DAY=`date +%A`
export PATH DAY
[ -d /root/emptydir ] || mkdir /root/emptydir
rsync --rsh=/usr/bin/ssh --delete -a /root/emptydir/
CENTRAL_SERVER_IP:/backup2/BACKED_UP_SERVER_FQDN/$DAY
rmdir /root/emptydir
rsync --delete
2018 Sep 11
1
Ensuring that rsync doesn't try to write to an unmounted drive
On Tue, 2018-09-11 at 12:56 -0400, Kevin Korb via rsync wrote:
> --timeout is about network connection timeouts. You aren't using the
> network so it doesn't apply at all. Even if you were networking an
> unmounted filesystem is an empty directory as far as rsync is
> concerned
> and rsync would treat it that way with no idea that you intended to
> have
> something
2008 Sep 09
2
Failed to retrieve password from secrets.tdb with anonymous bind
Samba 3.2.1 on linux OpenFiler 2.3
I have an external LDAP server with anonymous bind and pam
ProFtpd linked to LDAP server works well without error
But samba does not work, in smbd.log I have:
[2008/09/09 22:01:54, 0] passdb/secrets.c:fetch_ldap_pw(888)
fetch_ldap_pw: neither ldap secret retrieved!
[2008/09/09 22:01:54, 0] lib/smbldap.c:smbldap_connect_system(952)
ldap_connect_system:
2016 Mar 01
1
[PATCH] tests: move ntfs tests in a single directory
Move test-ntfscat.sh and test-ntfsclone.sh in a single ntfs directory,
much like the tests for other filesystems.
---
Makefile.am | 3 +-
configure.ac | 3 +-
tests/ntfs/Makefile.am | 27 +++++++++++++++++
tests/ntfs/test-ntfscat.sh | 53 +++++++++++++++++++++++++++++++++
tests/ntfs/test-ntfsclone.sh | 62
2008 Mar 06
2
rsync: Please add an option to ignore vanished files
Hi Everyone,
The following request was received from a Debian user; could you
comment on it? I think this seems reasonable, although the cron
output can be fixed by writing to a temporary file and using grep -v.
(The temporary file is necessary to avoid discarding the exit code,
although that may not be needed in the case of rsync, since it writes
that to stderr).
On Mon, Feb 20, 2006 at
2017 Nov 16
4
[Bug 13147] New: inconsistent behaviour regaring vanished files information
https://bugzilla.samba.org/show_bug.cgi?id=13147
Bug ID: 13147
Summary: inconsistent behaviour regaring vanished files
information
Product: rsync
Version: 3.0.9
Hardware: x64
OS: Mac OS X
Status: NEW
Severity: minor
Priority: P5
Component: core
Assignee:
2019 May 16
0
[Bug 13953] New: error message instead of --stats informations (in case of vanished files), using rsync 3.1.1 and rsync 3.0.9
https://bugzilla.samba.org/show_bug.cgi?id=13953
Bug ID: 13953
Summary: error message instead of --stats informations (in case
of vanished files), using rsync 3.1.1 and rsync 3.0.9
Product: rsync
Version: 3.1.1
Hardware: x64
OS: Linux
Status: NEW
Severity: normal
Priority: P5
2012 Nov 05
2
Issues with VANISHED CHANGEDSINCE
I've been seeing the following wonky behavior with Dovecot. Currently
this is with Dovecot 2.0.19, but I was also seeing it in earlier
versions as well, including versions from the 1.x series. Some
background, this is from Horde's ActiveSync library, when it is trying
to determine what UIDs have recently been expunged. I can guarantee
that when this command was sent, there was
2008 May 18
1
Some files vanished...
I run an rsync to backup my mail server ever 4 hours. Sometimes, I
get these sorts of warnings:
Rsyncing...
file has vanished: "/usr/local/virtual/*munged1*/new/
1210876129.43402_0.mail.server.tld"
file has vanished: "/usr/local/virtual/*munged2*/courierimapkeywords/.
4036254.1210876052.43312_0.mail.server.tld"
file has vanished: "/usr/local/virtual/*munged3*/cur/
2014 Jan 01
3
[Bug 10356] New: Include rsync-no-vanished support script
https://bugzilla.samba.org/show_bug.cgi?id=10356
Summary: Include rsync-no-vanished support script
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: All
Status: NEW
Severity: minor
Priority: P5
Component: core
AssignedTo: wayned at samba.org
ReportedBy: jakobunt at gmail.com
2004 Jan 07
1
2.6.0 "file has vanished" fails to set exit code on local client
A new 2.6.0 feature is supposed to use a different exit code when the
only 'errors' were from files that disappeared between the building
of the file list and the actual transfer of files.
But if the client is local and the server is remote, IOERR_VANISHED
gets set on the remote server, but is never passed to the local
client (the io_error value is passed at the end of the file list,
not
2004 Dec 14
0
[Bug 2158] New: Rsync discontinues when large files are vanished or updated
https://bugzilla.samba.org/show_bug.cgi?id=2158
Summary: Rsync discontinues when large files are vanished or
updated
Product: rsync
Version: 2.6.3
Platform: All
OS/Version: FreeBSD
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
2008 Jun 21
1
DO NOT REPLY [Bug 5554] New: File has vanished for files with foreign/unicode characters
https://bugzilla.samba.org/show_bug.cgi?id=5554
Summary: File has vanished for files with foreign/unicode
characters
Product: rsync
Version: 2.6.9
Platform: x86
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
2004 Jan 27
1
"file has vanished" bug [rsync-HEAD-20040127-1010GMT]
Just ran into this bug when running the latest snapshot from CVS: when
rsyncing from two source directories into a third one, rsync gets
confused about which source file is from which directory, resulting in a
"file vanished" error. See test script below.
Also, is there any consensus on whether using multiple source modules
when pulling from an rsync daemon is going to be ok? I
2007 Dec 07
1
exit code for vanished files in 2.6.9
I am using rsync 2.6.9 (as currently packaged in Mandriva 2007.1)
Ever since the latest update of the package I have been getting an exit
code of 23 with the output "file has vanished: {filename}".
For partial transfers due to vanished files, I (and my script) would
expect exit code 24.
(man page)
23 Partial transfer due to error
24 Partial transfer due to vanished source
2005 Oct 12
2
Vanished Files issue/enhancement
Hi Rsync/Samba team,
First of all, cudos on rsync 2.6.6! It is running exceptionally well.
I'm using a script executed by cron to keep warm-backup servers in sync
with the primary server. The execution is set to run every 5 minutes.
Like any good programmer, this process is *very* paranoid and uses
'wall' to notify the users if any error occurs during the transmissions.
This is