Re: [PATCH] open O_TEXT and O_BINARY for cygwin/windows
On Thu, Jan 23, 2003 at 01:55:40PM -0600, you [Dave Dykstra] wrote: > Why did you skip the fopen in log.c, which appends to the log file? I thought about that for a while. My reasoning was that the log file is probably read with unix/cygwin tools anyway - if not, the administrator is free to mount the filesystem binary or ascii. So I didn't want to enforce CR/LF on anyone. In general, I think forcing ascii makes more sense for reading than writing, because it in most imaginable cases will do no harm. > Because of the question about whether or not the "t" is ignored on all > platforms, I'm a little nervous about putting this into 2.5.6. It could be ifdefed, would it be safe to assume the following to work? #if !defined(O_TEXT) #define O_TEXT 0 #define O_TEXT_STR "" #else #define O_TEXT_STR "t" #endif #if !defined(O_BINARY) #define O_BINARY 0 #define O_BINARY_STR "" #else #define O_BINARY_STR "b" #endif and then instead of fopen(foo, "rt"); do this fopen(foo, "r" O_TEXT_STR); Comments? > I don't have any problem with it for 2.6.0. Maybe it should be just in > the 'patches' directory this time. > > Did you check to see whether any of the code that's reading config files > is ignoring carriage returns at the end of lines anyway? ISTR at least the password files were not recognized and I *think* rsync.conf was not parsed correctly when I originally wrote the patch. Looking at the source, though - exclude.c uses fgets() to read the lines from exclude file. I don't think it handles '\r' - param.c Ignores all '\r' in values, so rsync.conf should be fine. I'm not sure, whether reading the file as text would be more elegant (in theory there _could_ be other issues than the \r\n thing...) - authentivate.c seems to skip '\r' for passwords as well. So I guess you are right for the most crucial part of code (as of current rsync). -- v -- [EMAIL PROTECTED] -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: main.c error
On Thu, Jan 23, 2003 at 08:53:21PM -0600, Paul wrote: > Hello! This is not a real problem, since it seems to work correctly > anyway. But I'm still wondering about it. If I just execute "rsync" with > no switches or targets, it prints the usage, then gives an error at the > bottom: > > rsync error: syntax or usage error (code 1) at main.c(864) > > Is this normal, or indicating a bug, or what? It does this on three > different systems, so I don't think it is something I did. Rsync without any options or arguments is a usage error so the message is technically correct. It might be more precisely conformant to the documented usage to not output the usage message and just output the error but what would be the point? If you execute rsync -h no error is generated. I'd describe this as a user-friendly nit. Barely worth changing. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
main.c error
Hello! This is not a real problem, since it seems to work correctly anyway. But I'm still wondering about it. If I just execute "rsync" with no switches or targets, it prints the usage, then gives an error at the bottom: rsync error: syntax or usage error (code 1) at main.c(864) Is this normal, or indicating a bug, or what? It does this on three different systems, so I don't think it is something I did. Thanks, Paul -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
[patch] Still a problem with cleanup.c
Hello,
There is still a problem with the _exit_cleanup() function in
cleanup.c despite the patch that was put in last week that prevented
recursion. It turns out that sometimes multiple calls in close
sequence are done and this causes rsync to spin out of control
instead of exiting.
This bug was found by Marc Espie and the patch I'm including is
his as well. It hasn't been commited to the OpenBSD tree yet and
is still undergoing testing but it does fix the immediate easily
detectable problem. His post with the bug fix was here:
http://marc.theaimsgroup.com/?l=openbsd-tech&m=104238879828005&w=2
I've changed the variable names to match what is in the rsync
tree already.
This bug is easily triggerable with a local rsync copy.
rsync -av /some/reasonably/large/dir /tmp/somewhere
Wait until after the copy has started (after it is done with
building the file list) and then hit ctrl-c. Watch rsync fill
the screen with messages like:
rsync: connection unexpectedly closed (94819 bytes read so far)
rsync: connection unexpectedly closed (94819 bytes read so far)
rsync: connection unexpectedly closed (94819 bytes read so far)
Curse.
Switch to another window and kill -9 the errant rsync process.
Apply patch and notice it no longer goes crazy.
-b
Index: cleanup.c
===
RCS file: /cvsroot/rsync/cleanup.c,v
retrieving revision 1.15
diff -u -r1.15 cleanup.c
--- cleanup.c 16 Jan 2003 20:09:31 - 1.15
+++ cleanup.c 24 Jan 2003 01:24:09 -
@@ -63,11 +63,11 @@
extern int log_got_error;
static int inside_cleanup = 0;
- if (inside_cleanup != 0) {
+ if (inside_cleanup > 10) {
/* prevent the occasional infinite recursion */
return;
}
- inside_cleanup = 1;
+ inside_cleanup++;
signal(SIGUSR1, SIG_IGN);
signal(SIGUSR2, SIG_IGN);
Index: cleanup.c
===
RCS file: /cvsroot/rsync/cleanup.c,v
retrieving revision 1.15
diff -u -r1.15 cleanup.c
--- cleanup.c 16 Jan 2003 20:09:31 - 1.15
+++ cleanup.c 24 Jan 2003 01:24:09 -
@@ -63,11 +63,11 @@
extern int log_got_error;
static int inside_cleanup = 0;
- if (inside_cleanup != 0) {
+ if (inside_cleanup > 10) {
/* prevent the occasional infinite recursion */
return;
}
- inside_cleanup = 1;
+ inside_cleanup++;
signal(SIGUSR1, SIG_IGN);
signal(SIGUSR2, SIG_IGN);
Resume not working
Title: Message Hi, I ran out of disk space while getting ISOs doing: rsync -Pavz machinename::path/to/directory targetdir When I deleted some stuff and used the same command to resume, I got an error (code 12) at io.c (165). I had to delete the file in order to resume. Later, the connection simply stopped sending new bytes so I cancelled (Ctrl-C) and attempted to rsync from a different mirror. Attempting to resume using the different server gave me a similar error (code 12) at io.c (177). I'm using Gentoo Linux with Rsync 2.5.6_pre20021105_r1 on a Pentium II machine. No proxys or anything weird. Anyway, I think the program's great as is, but I figured in case this was somehow vital information that you had been urgently wishing for which had never been reported, I might as well send a paltry e-mail. My guess is you know all about it. -Steve
aix 4.3 or 5
Hi, Where can I find rsync 2.5.5 for aix ? Thanks.
Re: Error message
With file sizes over 2GB I'd suspect problems with >31-bit numbers being returned from stat() et. al. The rsync version you have on AIX is very old, and more recent versions handle large files better. The first thing to do is to upgrade rsync your AIX machine. - Dave On Thu, Jan 23, 2003 at 01:44:42PM +0100, Michael Salmon wrote: > On Thursday, January 23, 2003 12:36:52 PM +0100 Boris Gegenheimer > <[EMAIL PROTECTED]> wrote: > +-- > | The versions of the different machines I use are the initiating machine : > | Sun 450 > | Solaris 8 > | Rsync 2.5.5 > | > | The machine that I try to copy from : > | IBM rs6000 > | AIX 4.3 > | Rsync 2.3.1 > | > | The command I use is > | /usr/local/bin/rsync -au -q --stats --progress > | --rsync-path=/usr/local/bin/rsync maximus:/ptsfs2 > | /diskbackup/kanal1/maximus/ > | > | The error message comes when he tries to copy that file mentioned below > | which is 14GB big it is not the filesystem or the name of the file because > | it worked with ncftpget. > | But that program has other problems that I will not mention here. > [...] > | On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote: > | > Hello when i get this message what is wrong: > | > > | > /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large > | > to be stored in data type > | > > | > Regards Boris > [...] > +-X8 > > I have also seen that message with times before 1970. This is the standard > text for EOVERFLOW. > > /Michael > -- > This space intentionally left non-blank. > -- > To unsubscribe or change options: > http://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
how to send only the diff ?
Hi, I’m trying to do so that rsync does not send a file that exists but is different on the remote. I want rsync to send only the difference to the remote. I prefer to send the difference of a 500 MB file than sending the whole file over. I use AIX and rsync version rsync version 2.4.5 protocol version 24 Oh and my command is : rsync --stats --progress --delete --partial --timeout=60 --bwlimit=10 -aRtvz patrick@risc1::test /special thank you.
Re: Rsyncing of block devices to a remote file
I'm not sure why it would really need to know the size, but given that it wants it, can you open the file and lseek to the end of it? - Dave Dykstra On Thu, Jan 23, 2003 at 09:17:04AM +0100, David Heremans wrote: > Hello, > > I'm looking for some assistance in modifying the rsync code > > Situation: I used to back-up some of my (unmounted NTFS) disk partitions > remotely using the following shells construct: > dd if=/dev/hda1 | gzip | ssh me@backupmachine 'cat > > /backup-dir/hda1-backup.gz' > > But now I want to use rsync for this, since transfering 10 gig takes a litle > to long if a file of a few kB has changed :-). I looked trough the archive > and found an old mail talking about the same problem, and a response > explaining the problem of writting to a block device (since rsync writes a > copy file and then moves it over the original). But the same mail also said > that reading from it should be trivial, so I set out trying to implement > this. > > So I created a '--read-block-file' option in options.c and avoided the > 'skipping non regular file' message in generator.c > By altering all this the receiver is ready to get the data, but in the flist > structure it still says that '/dev/hda1' is still a devicefile > and that the size is 0, and so the sender does send over zero bytes > > Now here is the problem : How do I get the size of partition in this > datastructure ? Or more generique, how would I handle this for /dev/fd0, > since you can insert 1.44MB disks or 720kB disks ? > > Anybody else tried to read blockdevices over rsync already ? > > After all, sending the data of a block device doesn't seem to be as trivial > as the archived mail sugested :-) > > David > > -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
n00b needing help with rsync + win 9x
hi, my first post here. i have knoppix linux 3.1 jan 01 release in iso format i want to update it to jan 20th release. i installed rsync for win 9x minimalist approach http://optics.ph.unimelb.edu.au/help/rsync/rsync_pc1.html command i used was : rsync246 -e ssh -avP rsync://ftp.gwdg.de/pub/linux/knoppix/KNOPPIX_V3.1-2003-01-20-EN.iso KNOPPIX_V3.1-2003-01-01-EN.iso i was able to connect to server, downloaded the filelist, and it started to update the ISO. the speed was extremly slow compared to jigdo...it was taking the same amount of time as to download the whole cd again. can anyone plz throw some light on this !!! am i doing anything wrong ??? also, the size it shows while updating the file is in bytes or kilobytes ?? __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: [PATCH] open O_TEXT and O_BINARY for cygwin/windows
Why did you skip the fopen in log.c, which appends to the log file?
Because of the question about whether or not the "t" is ignored on all
platforms, I'm a little nervous about putting this into 2.5.6. I don't
have any problem with it for 2.6.0. Maybe it should be just in the
'patches' directory this time.
Did you check to see whether any of the code that's reading config files
is ignoring carriage returns at the end of lines anyway?
- Dave
On Thu, Jan 23, 2003 at 09:49:02AM +0200, Ville Herva wrote:
> > > perhaps you would want to consider the "force binary open for data files
> > > on CYGWIN" -patch I sent ages ago? I feel it's quite important, and to
> > > me it never makes sense to open data files in ascii (CR/LF translation
> > > mode) nor config files in BINARY mode (opening them in ascii makes it
> > > possible to edit them with both NOTEPAD etc and the unix line ending
> > > compliant cygwin editors.)
> > >
> > > See the thread starting at:
> > >
> > >
>http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=utf-8&threadm=a4vfnh%242ec%241%40FreeBSD.csie.NCTU.edu.tw&rnum=1&prev=/groups%3Fq%3Drsync%2Bon%2Bcygwin%2B-%2Btextmode%2Bconfig%2Bfiles%26num%3D50%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3Dutf-8%26sa%3DN%26tab%3Dwg
> > >
> > > I'm mostly talking about (4) - others are not that important.
>
> On Wed, Jan 22, 2003 at 03:53:27PM -0600, you [Dave Dykstra] wrote:
> > Could you please port the patch to 2.5.6pre2 and post it to the mailing
> > list?
>
> Here it is.
>
> In short: on Cygwin you can mount volumes as text or binary. For text mounts
> CR/LF->CR translation is done on the fly, binary mounts do not alter the
> data. For applications that deal with raw data (gzip, tar, md5sum, cp,
> rsync) it makes sense to access the data in binary always (and actually
> rsync does nowadays, the O_BINARY flag is set in do_open). On the other hand
> it makes sense to open config files in text so that the user can change
> them with windows editors - the CR/LF translation will do no harm even if
> the file has unix line endings.
>
> This batch adds a few O_TEXT and O_BINARY flags to *open() calls - files
> that are obviously text are opened as such; data files are opened as
> binary.
>
> - Files batch.c checksum.c generator.c receiver.c sender.c util.c use
> do_open which does O_BINARY already (which has chanced since I originally
> made the patch years ago), so no need to touch those. Other than that
> I went through all open, fdopen, and fopen calls and tried to
> add either O_TEXT or O_BINARY where it made sense.
> - O_BINARY and O_TEXT are defined in rsync.h unless they are available
> on the platform:
>
>+#if !defined(O_TEXT)
>+#define O_TEXT 0
>+#endif
>+#if !defined(O_BINARY)
>+#define O_BINARY 0
>+#endif
>
> - I also use fopen(filename, "rt"). I _think_ that all fopen implementations
> should ignore "t" unless they recognize it. At least linux does (it
> seems to ignore all chars it doesn't recognize. "rt" is one of the
> alternatives Chris Faylor recommends for CYGWIN:
>
> http://www.cygwin.com/ml/cygwin/2000-10/msg00213.html:
> > You do that one of three ways:
> >
> > open ("foo", O_RDONLY | O_TEXT);
> > fopen ("foo", "rt");
> > setmode (fd, O_TEXT);
>
> "rt" one is the only one for FILEs (and setmode doesn't even exists on
> all other platforms AFAICT.
>
> man fopen says:
>
>The mode string can also include the letter ``b'' either
>as a last character or as a character between the charac
>ters in any of the two-character strings described above.
>This is strictly for compatibility with ANSI X3.159-1989
>(``ANSI C'') and has no effect; the ``b'' is ignored on
>all POSIX conforming systems, including Linux. (Other
>systems may treat text files and binary files differently,
>and adding the ``b'' may be a good idea if you do I/O to a
>binary file and expect that your program may be ported to
>non-Unix environments.)
>
> So I would hope that "t" is handled the same way.
>
> Anyway, if someone knows better, please tell.
>
> Patch attached - compiled, briefly tested (the previous incarnations tested
> pretty extensively.) It doesn't alter the behaviour on platforms that don't
> do O_BINARY and O_TEXT differently so I thinks it should be quite safe to
> apply.
>
>
> -- v --
>
> [EMAIL PROTECTED]
> diff -Naur --show-c-function --exclude='*.o' --exclude='*.exe' --exclude=Makefile
>--exclude='*~' rsync-2.5.6pre2.ORIG/authenticate.c rsync-2.5.6pre2/authenticate.c
> --- rsync-2.5.6pre2.ORIG/authenticate.c 2002-08-01 03:40:13.0 +0300
> +++ rsync-2.5.6pre2/authenticate.c2003-01-23 08:56:09.0 +0200
> @@ -82,7 +82,7 @@ static int get_secret(int module, char *
>
> if (!fname || !*fname) return 0;
>
> - fd = open(fname,O_RDONLY);
> + fd = open(fname,O_RDONLY | O_TEXT);
> if (fd == -1) r
how to send only the diff ?
Hi, I’m trying to do so that rsync does not send a file that exists but is different on the remote. I want rsync to send only the difference to the remote. I prefer to send the difference of a 500 MB file than sending the whole file over. I use AIX and rsync version rsync version 2.4.5 protocol version 24 Oh and my command is : rsync --stats --progress --delete --partial --timeout=60 --bwlimit=10 -aRtvz patrick@risc1::test /special thank you.
Re: Please test rsync-2.5.6pre2
On Tue, Jan 21, 2003 at 08:00:51PM -0801, Jos Backus wrote: > On Mon, Jan 20, 2003 at 10:19:42PM -0600, Dave Dykstra wrote: > > The second rsync-2.5.6 pre-release version is now available at: > > There's the popt-1.7 update (with Dave's sprintf() workaround) at > > http://www.catnook.com/patches/rsync-popt-1.7.diff > > Perhaps we can apply this after the release as it is a very low priority > update; I'd just like it not to rot :) Yes, it should go in after the 2.5.6 release. - Dave -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: send_files failed to open filename ...
jw schultz wrote: * is these messages harmful or not ? Not harmful. It is an indication of the volatility of the source at the time of transfer. Having some files disappear could result in an inconsistant state. For example: a web repository where the delete happens between index.html and gif or link destinations on which it depends. Just a caution. It could be worthwhile to test the log for these messages and rerun if their count exeeds some threshold, say zero. For an active site i'd suggest double-buffering. Ok, Thanks much, but I don't really understand this last part, especially the *double buffering* ? Regards, -- Do-Risika RAFIEFERANTSIARONJY, SysAdmin mailto:[EMAIL PROTECTED] Simicro Internet, mailto:[EMAIL PROTECTED], http://internet.simicro.mg Tel : (+261) 20 22 648 83 (GMT +3), Fax : (+261) 20 22 661 83 -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
SUMMARY: Error message
I found the reason I think anyway. It was the different versions of rsync on the 2 machines. I upgraded the one on the AIX machine and then it copied just fine. Thank you jw and Michael for answering. Boris -Original Message- From: Michael Salmon [mailto:[EMAIL PROTECTED]] Sent: 23. januar 2003 13:45 To: [EMAIL PROTECTED] Subject: RE: Error message On Thursday, January 23, 2003 12:36:52 PM +0100 Boris Gegenheimer <[EMAIL PROTECTED]> wrote: +-- | The versions of the different machines I use are the initiating | machine : Sun 450 Solaris 8 | Rsync 2.5.5 | | The machine that I try to copy from : | IBM rs6000 | AIX 4.3 | Rsync 2.3.1 | | The command I use is | /usr/local/bin/rsync -au -q --stats --progress | --rsync-path=/usr/local/bin/rsync maximus:/ptsfs2 | /diskbackup/kanal1/maximus/ | | The error message comes when he tries to copy that file mentioned | below which is 14GB big it is not the filesystem or the name of the | file because it worked with ncftpget. But that program has other | problems that I will not mention here. [...] | On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote: | > Hello when i get this message what is wrong: | > | > /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too | > large to be stored in data type | > | > Regards Boris [...] +-X8 I have also seen that message with times before 1970. This is the standard text for EOVERFLOW. /Michael -- This space intentionally left non-blank. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: send_files failed to open filename ...
On Thu, Jan 23, 2003 at 03:38:34PM +0300, Do-Risika RAFIEFERANTSIARONJY wrote: > > Hi everybody, > > I'm mirroring some websites with rsync (daemon on the source), and I > noticed in the destination host some error messages 'send_files failed > to open filenames', > > Actually, the concerned files are deleted on the source host, but I > would like to ask : > > * why does rsync say these (in which phase) ? Because the files were deleted from the source between the initial tree scan and send_files. These would be files that meta-data indicates are changed. send_files is what calculates and sends the deltas. > * is these messages harmful or not ? Not harmful. It is an indication of the volatility of the source at the time of transfer. Having some files disappear could result in an inconsistant state. For example: a web repository where the delete happens between index.html and gif or link destinations on which it depends. Just a caution. It could be worthwhile to test the log for these messages and rerun if their count exeeds some threshold, say zero. For an active site i'd suggest double-buffering. > Here below my rsync command and some of the error messages : > > rsync --delete -zrv --bwlimit=$bwlimit --timeout=1200 > --exclude-from='/etc/rsync/exclude' $user\@" . $server . > "::htdocs/$dir/ /var/www/htdocs/$dir/ > > > send_files failed to open > www.lft.mg/matieres/svt/Evaluations/CLASSE.GIF: No such file or directory > send_files failed to open > www.lft.mg/matieres/svt/Evaluations/COUPES.GIF: No such file or directory > send_files failed to open > www.lft.mg/matieres/svt/Evaluations/DBasalte.gif: No such file or directory > send_files failed to open > www.lft.mg/matieres/svt/Evaluations/SCHMA.gif: No such file or directory [snip] -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
RE: Error message
On Thursday, January 23, 2003 12:36:52 PM +0100 Boris Gegenheimer <[EMAIL PROTECTED]> wrote: +-- | The versions of the different machines I use are the initiating machine : | Sun 450 | Solaris 8 | Rsync 2.5.5 | | The machine that I try to copy from : | IBM rs6000 | AIX 4.3 | Rsync 2.3.1 | | The command I use is | /usr/local/bin/rsync -au -q --stats --progress | --rsync-path=/usr/local/bin/rsync maximus:/ptsfs2 | /diskbackup/kanal1/maximus/ | | The error message comes when he tries to copy that file mentioned below | which is 14GB big it is not the filesystem or the name of the file because | it worked with ncftpget. | But that program has other problems that I will not mention here. [...] | On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote: | > Hello when i get this message what is wrong: | > | > /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large | > to be stored in data type | > | > Regards Boris [...] +-X8 I have also seen that message with times before 1970. This is the standard text for EOVERFLOW. /Michael -- This space intentionally left non-blank. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
send_files failed to open filename ...
Hi everybody, I'm mirroring some websites with rsync (daemon on the source), and I noticed in the destination host some error messages 'send_files failed to open filenames', Actually, the concerned files are deleted on the source host, but I would like to ask : * why does rsync say these (in which phase) ? * is these messages harmful or not ? Here below my rsync command and some of the error messages : rsync --delete -zrv --bwlimit=$bwlimit --timeout=1200 --exclude-from='/etc/rsync/exclude' $user\@" . $server . "::htdocs/$dir/ /var/www/htdocs/$dir/ send_files failed to open www.lft.mg/matieres/svt/Evaluations/CLASSE.GIF: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/COUPES.GIF: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/DBasalte.gif: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/SCHMA.gif: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/TPE2002.htm: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/artriole_veine.htm: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/clip_image0020.gif: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/dorsaleatlantique.gif: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/ficaire.jpg: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/follicule2.jpg: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/jbc_1.htm: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/jcb_0.htm: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/macrophage.jpg: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/merthyrnienne.gif: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/profilsismreflex.gif: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/subduc.gif: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/test.htm: No such file or directory send_files failed to open www.lft.mg/matieres/svt/Evaluations/wlsctop1.gif: No such file or directory Thanks in advance, -- Do-Risika RAFIEFERANTSIARONJY, SysAdmin mailto:[EMAIL PROTECTED] Simicro Internet, mailto:[EMAIL PROTECTED], http://internet.simicro.mg Tel : (+261) 20 22 648 83 (GMT +3), Fax : (+261) 20 22 661 83 -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: Error message
On Thu, Jan 23, 2003 at 12:36:52PM +0100, Boris Gegenheimer wrote: > The versions of the different machines I use are the initiating machine : > Sun 450 > Solaris 8 > Rsync 2.5.5 > > The machine that I try to copy from : > IBM rs6000 > AIX 4.3 > Rsync 2.3.1 > > The command I use is > /usr/local/bin/rsync -au -q --stats --progress > --rsync-path=/usr/local/bin/rsync maximus:/ptsfs2 > /diskbackup/kanal1/maximus/ > > The error message comes when he tries to copy that file mentioned below > which is 14GB big it is not the filesystem or the name of the file because > it worked with ncftpget. > But that program has other problems that I will not mention here. > > Regards Boris You might check the error strings in /usr/include. I haven't either of those systems available to me to check. I can say that a 14GB file may have some issues with the checksum blocksize. With the default blocksize of 700 the file will use some 20 million block checksums which is likely to cause collision problems. Try using --block-size=32768 I can't say that is the problem but even if it isn't a large blocksize is in order. Version 2.5.6 will have an adaptive block-size. > -Original Message- > From: jw schultz [mailto:[EMAIL PROTECTED]] > Sent: 23. januar 2003 11:34 > To: '[EMAIL PROTECTED]' > Subject: Re: Error message > > > On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote: > > Hello when i get this message what is wrong: > > > > /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large > > to be stored in data type > > > > Regards Boris > > Dunno. That error message is not in the rsync source. > Since you don't say what platforms are involved, what the commandline or > other config info is, the context of the message, or what version of rsync > it would be difficult to say. > > My best guess is that the filename is too long for the destination > filesystem but that seems unlikely because rsync creates its own error > messages for that. > > Confirm that you can create a file 10 chars longer than the actual file then > try again with more info. > > -- > > J.W. SchultzPegasystems Technologies > email address: [EMAIL PROTECTED] > > Remember Cernan and Schmitt > -- > To unsubscribe or change options: > http://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html > -- > To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
RE: Error message
The versions of the different machines I use are the initiating machine : Sun 450 Solaris 8 Rsync 2.5.5 The machine that I try to copy from : IBM rs6000 AIX 4.3 Rsync 2.3.1 The command I use is /usr/local/bin/rsync -au -q --stats --progress --rsync-path=/usr/local/bin/rsync maximus:/ptsfs2 /diskbackup/kanal1/maximus/ The error message comes when he tries to copy that file mentioned below which is 14GB big it is not the filesystem or the name of the file because it worked with ncftpget. But that program has other problems that I will not mention here. Regards Boris -Original Message- From: jw schultz [mailto:[EMAIL PROTECTED]] Sent: 23. januar 2003 11:34 To: '[EMAIL PROTECTED]' Subject: Re: Error message On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote: > Hello when i get this message what is wrong: > > /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large > to be stored in data type > > Regards Boris Dunno. That error message is not in the rsync source. Since you don't say what platforms are involved, what the commandline or other config info is, the context of the message, or what version of rsync it would be difficult to say. My best guess is that the filename is too long for the destination filesystem but that seems unlikely because rsync creates its own error messages for that. Confirm that you can create a file 10 chars longer than the actual file then try again with more info. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: Error message
On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote: > Hello when i get this message what is wrong: > > /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large to be > stored in data type > > Regards Boris Dunno. That error message is not in the rsync source. Since you don't say what platforms are involved, what the commandline or other config info is, the context of the message, or what version of rsync it would be difficult to say. My best guess is that the filename is too long for the destination filesystem but that seems unlikely because rsync creates its own error messages for that. Confirm that you can create a file 10 chars longer than the actual file then try again with more info. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Error message
Title: Message Hello when i get this message what is wrong: /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large to be stored in data type Regards Boris
Re: Rsyncing of block devices to a remote file
On Thu, Jan 23, 2003 at 09:17:04AM +0100, David Heremans wrote: > Hello, > > I'm looking for some assistance in modifying the rsync code > > Situation: I used to back-up some of my (unmounted NTFS) disk partitions > remotely using the following shells construct: > dd if=/dev/hda1 | gzip | ssh me@backupmachine 'cat > > /backup-dir/hda1-backup.gz' > > But now I want to use rsync for this, since transfering 10 gig takes a litle > to long if a file of a few kB has changed :-). I looked trough the archive > and found an old mail talking about the same problem, and a response > explaining the problem of writting to a block device (since rsync writes a > copy file and then moves it over the original). But the same mail also said > that reading from it should be trivial, so I set out trying to implement > this. > > So I created a '--read-block-file' option in options.c and avoided the > 'skipping non regular file' message in generator.c > By altering all this the receiver is ready to get the data, but in the flist > structure it still says that '/dev/hda1' is still a devicefile > and that the size is 0, and so the sender does send over zero bytes > > Now here is the problem : How do I get the size of partition in this > datastructure ? Or more generique, how would I handle this for /dev/fd0, > since you can insert 1.44MB disks or 720kB disks ? > > Anybody else tried to read blockdevices over rsync already ? > > After all, sending the data of a block device doesn't seem to be as trivial > as the archived mail sugested :-) I do not believe that this is portable. There may be ioctl command(s) to retrieve this information. Most likely you will need to fetch block size and counts seperately and do the artithmatic. I recall indications that linux may obsolete this method and moving this to sysfs or driverfs but i could be mistaken. In any event there is no requirement that all OSs use the same method. If you can't find it in the documentation try looking at the source code for a mkfs command for your OS or run one with a strace supervisor. Alternatively dd if=/dev/hda1 | gzip >hda1-backup.gz; rsync hda1-backup.gz me@backupmachine/backup-dir/hda1-backup.gz and you'll get much better results with the rsync friendly patch to gzip. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Rsyncing of block devices to a remote file
Title: Rsyncing of block devices to a remote file Hello, I'm looking for some assistance in modifying the rsync code Situation: I used to back-up some of my (unmounted NTFS) disk partitions remotely using the following shells construct: dd if=/dev/hda1 | gzip | ssh me@backupmachine 'cat > /backup-dir/hda1-backup.gz' But now I want to use rsync for this, since transfering 10 gig takes a litle to long if a file of a few kB has changed :-). I looked trough the archive and found an old mail talking about the same problem, and a response explaining the problem of writting to a block device (since rsync writes a copy file and then moves it over the original). But the same mail also said that reading from it should be trivial, so I set out trying to implement this. So I created a '--read-block-file' option in options.c and avoided the 'skipping non regular file' message in generator.c By altering all this the receiver is ready to get the data, but in the flist structure it still says that '/dev/hda1' is still a devicefile and that the size is 0, and so the sender does send over zero bytes Now here is the problem : How do I get the size of partition in this datastructure ? Or more generique, how would I handle this for /dev/fd0, since you can insert 1.44MB disks or 720kB disks ? Anybody else tried to read blockdevices over rsync already ? After all, sending the data of a block device doesn't seem to be as trivial as the archived mail sugested :-) David
