[Bug 12522] [PATCH] Send last error messages to sender

2020-05-26 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=12522

Ben RUBSON  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|NEW |RESOLVED

--- Comment #4 from Ben RUBSON  ---
Patch moved : https://github.com/WayneD/rsync/pull/2

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


[Bug 12522] [PATCH] Send last error messages to sender

2018-02-13 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=12522

Ben RUBSON <ben.rub...@gmail.com> changed:

   What|Removed |Added

  Attachment #12841|0   |1
is obsolete||

--- Comment #3 from Ben RUBSON <ben.rub...@gmail.com> ---
Created attachment 13959
  --> https://bugzilla.samba.org/attachment.cgi?id=13959=edit
Send last error messages to sender

Modified patch to seamlessly suit rsync 3.1.3.
Thx !

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


[Bug 12522] [PATCH] Send last error messages to sender

2017-01-18 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=12522

Ben RUBSON <ben.rub...@gmail.com> changed:

   What|Removed |Added

  Attachment #12838|0   |1
is obsolete||

--- Comment #2 from Ben RUBSON <ben.rub...@gmail.com> ---
Created attachment 12841
  --> https://bugzilla.samba.org/attachment.cgi?id=12841=edit
Send last error messages to sender

Error correction on sender side.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


[Bug 12522] New: [PATCH] Send last error messages to sender

2017-01-16 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=12522

Bug ID: 12522
   Summary: [PATCH] Send last error messages to sender
   Product: rsync
   Version: 3.1.2
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P5
 Component: core
  Assignee: way...@samba.org
  Reporter: ben.rub...@gmail.com
QA Contact: rsync...@samba.org

Created attachment 12832
  --> https://bugzilla.samba.org/attachment.cgi?id=12832=edit
Send last error messages to sender

Hello,

Here is a patch which sends last error messages to sender for a file-transfer
which failed.

It helps especially with protocol < 31.

This can be useful for example to know that a FS is full.

Thank you !

Ben



### Without :

/repository/mybigfile.iso
539.26M   6%   11.21MB/s0:11:01  
rsync: [sender] write error: Broken pipe (32)
rsync error: error in file IO (code 11) at io.c(831) [sender=3.1.2]



### With (of course the interesting message here is the first one) :

/repository/mybigfile.iso
539.26M   6%   11.21MB/s0:11:01  
rsync: write failed on "/repository/mybigfile.iso" (in bkp): Disc quota
exceeded (69)
rsync error: error in file IO (code 11) at receiver.c(400) [receiver=3.1.2]
rsync error: error in file IO (code 11) at io.c(1633) [generator=3.1.2]
rsync: [sender] write error: Broken pipe (32)
rsync error: error in file IO (code 11) at io.c(831) [sender=3.1.2]

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


[Bug 10445] New: flag to suppress link_stat error messages

2014-02-13 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10445

   Summary: flag to suppress link_stat error messages
   Product: rsync
   Version: 3.1.1
  Platform: All
OS/Version: All
Status: NEW
  Severity: enhancement
  Priority: P5
 Component: core
AssignedTo: way...@samba.org
ReportedBy: m...@bitchx.it
 QAContact: rsync...@samba.org


rsync complains about file arguments not existing.

For example, running this command to archive a selected set of files:

rsync -aq --remove-from-source --remove-source-files /var/log/messages*bz2
/backup/maillog*bz2 /backup/auth.log*bz2 backupserver::myname/

will issue the following errors if any of the given patters has no match:

rsync: link_stat /var/log/messages*bz2 failed: No such file or directory (2)
rsync: link_stat /backups/maillog*bz2 failed: No such file or directory (2)
...

One particular application of commands similar to this is to periodically save
archives to a central backup server via cron. This causes cron to periodically
mail admins with the above errors. The option to divert this to /dev/null is
dangerous, as it would lose other error messages which ARE actually useful,
such as failures to reach the backup server.

A command line argument such as --ignore-missing-files that avods this type of
errors (link_stat) would do great.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the bug.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


[Bug 10445] flag to suppress link_stat error messages

2014-02-13 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10445

michele m...@bitchx.it changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID

--- Comment #1 from michele m...@bitchx.it 2014-02-13 18:28:22 UTC ---
I see that the newest version of rsync does support this as
--ignore-missing-args . The manpage on the Mac tricked me to assume
otherwise. Closing this, sorry for the noise.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the bug.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: Error messages 3.0.6pre1

2009-07-23 Thread Warren Oates
On Wed, Jul 22, 2009 at 2:52 AM, Mac User FRmacuse...@free.fr wrote:
 This is a malloc (memory allocation) error.
 It shows that a non-aligned pointer (pointer that doesn't start on an
 address multiple of 4 in a 32-bit machine) is being freed. As pointers must
 always be aligned, this indicates an error and the function free() doesn't
 know how to deal with it. But even if it doesn't release the memory at all,
 there are big chances that rsync ends up the execution normally. The only
 issue is a possible memory leak that is normally stopped when rsync exit.

 I didn't look nor am aware of the rsync code, but I guess this could be an
 issue of 32-bit pointer on a 64-bit machine.

 Best regards,

 Vitorio


Hmm. Out of curiosity, I recompiled rsync as a 64-bit application, and
the same error comes up.
Something like this if you're interested (iconv won't work):

# MACOSX_DEPLOYMENT_TARGET=10.5
# CFLAGS=”-arch x86_64 -g -Os -pipe -no-cpp-precomp”
# CCFLAGS=”-arch x86_64 -g -Os -pipe”
# CXXFLAGS=”-arch x86_64 -g -Os -pipe”
# LDFLAGS=”-arch x86_64 -bind_at_load”
# export CFLAGS CXXFLAGS LDFLAGS CCFLAGS MACOSX_DEPLOYMENT_TARGET

This is arcane stuff, beyond my abilities or knowledge of programming.
As for Mat Cohen's question about the Xcode version, try:

xcodebuild -version

at your prompt.

-- 
W. Oates
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: Error messages 3.0.6pre1

2009-07-22 Thread Mac User FR

This is a malloc (memory allocation) error.
It shows that a non-aligned pointer (pointer that doesn't start on an  
address multiple of 4 in a 32-bit machine) is being freed. As pointers  
must always be aligned, this indicates an error and the function  
free() doesn't know how to deal with it. But even if it doesn't  
release the memory at all, there are big chances that rsync ends up  
the execution normally. The only issue is a possible memory leak that  
is normally stopped when rsync exit.


I didn't look nor am aware of the rsync code, but I guess this could  
be an issue of 32-bit pointer on a 64-bit machine.


Best regards,

Vitorio

Le 21 juil. 09 à 21:32, Warren Oates a écrit :


On Mon, Jul 20, 2009 at 4:20 AM, Mark Cohenmarkco...@mac.com wrote:
I too have the same issue (reported by Warren) - in that 3.06  
backups appear

valid, but the terminal shows the following errors:

rsync(18819) malloc: *** error for object 0xf305c: Non-aligned  
pointer being

freed
*** set a breakpoint in malloc_error_break to debug

I'm looking for confirmation that these are simply anomalies, and  
indeed are

not cause for concern.

Thanks.
--
Please use reply-all for most replies to avoid omitting the mailing  
list.

To unsubscribe or change options:
https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html



I have a draft email almost ready for the list about this. I have a
feeling it has to do with the latest version of the Xcode tools in
10.5.7 (DevToolsCore-1148.0) which provides gcc version 4.0.1 build
5490. My wife's MacBook is  DevToolsCore-921.0 with build 5465 of the
same gcc, and I don't think the error occurs when I use rsync the
other way.. I'm not sure of this, because I've been a bit busy to do
more testing, which is why my email is still in draft. At any rate,
the error only _seems_ to have started when I updated Xcode.

If you Google for that error, some interesting discussions pop up.

--
W. Oates
--
Please use reply-all for most replies to avoid omitting the mailing  
list.

To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: Error messages 3.0.6pre1

2009-07-21 Thread Warren Oates
On Mon, Jul 20, 2009 at 4:20 AM, Mark Cohenmarkco...@mac.com wrote:
 I too have the same issue (reported by Warren) - in that 3.06 backups appear
 valid, but the terminal shows the following errors:

 rsync(18819) malloc: *** error for object 0xf305c: Non-aligned pointer being
 freed
 *** set a breakpoint in malloc_error_break to debug

 I'm looking for confirmation that these are simply anomalies, and indeed are
 not cause for concern.

 Thanks.
 --
 Please use reply-all for most replies to avoid omitting the mailing list.
 To unsubscribe or change options:
 https://lists.samba.org/mailman/listinfo/rsync
 Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


I have a draft email almost ready for the list about this. I have a
feeling it has to do with the latest version of the Xcode tools in
10.5.7 (DevToolsCore-1148.0) which provides gcc version 4.0.1 build
5490. My wife's MacBook is  DevToolsCore-921.0 with build 5465 of the
same gcc, and I don't think the error occurs when I use rsync the
other way.. I'm not sure of this, because I've been a bit busy to do
more testing, which is why my email is still in draft. At any rate,
the error only _seems_ to have started when I updated Xcode.

If you Google for that error, some interesting discussions pop up.

-- 
W. Oates
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


re: Error messages 3.0.6pre1

2009-07-20 Thread Mark Cohen
I too have the same issue (reported by Warren) - in that 3.06 backups  
appear valid, but the terminal shows the following errors:


rsync(18819) malloc: *** error for object 0xf305c: Non-aligned pointer  
being freed

*** set a breakpoint in malloc_error_break to debug

I'm looking for confirmation that these are simply anomalies, and  
indeed are not cause for concern.


Thanks.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: Error messages 3.0.6pre1

2009-04-25 Thread Wayne Davison
On Fri, Apr 17, 2009 at 03:03:02PM -0400, Warren Oates wrote:
 I compiled 3.0.6pre1, including  the crtimes and fileflags patches for
 use on Intel OS X 10.5.6

I just compiled rsync with those patches on an Intel OS X 10.5.6 system,
and didn't see any such errors.  I did see an issue with make check
(an output problem in the daemon test's file listing) which pointed me
at an issue with --list-only's handling of create times.  I've fixed
that for the next release.

Do you see free warnings for all rsync copies?  What does file rsync
say for the rsync binary?  I'd suggest building your own rsync, and if
the errors continue, I'll need some help to figure out what free is
causing them.

..wayne..
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Error messages 3.0.6pre1

2009-04-17 Thread Warren Oates
I compiled 3.0.6pre1, including  the crtimes and fileflags patches for
use on Intel OS X 10.5.6, as described by Mr. Bombich (thanks!) here:
http://www.bombich.com/mactips/rsync.html

I want to use 3.0.6 because it seems that this bug:
https://bugzilla.samba.org/show_bug.cgi?id=5365
has been resolved (yay!).


-
[~]$ rsync --version
rsync  version 3.0.6pre1  protocol version 30
Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
64-bit files, 32-bit inums, 32-bit timestamps, 64-bit long ints,
socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
append, ACLs, xattrs, iconv, symtimes, file-flags
-

However, now I'm getting these kinds of messages throughout my output:

-
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard sketch. 01.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard sketch 00.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard 03.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard 02.psd
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard 02.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard 01.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leanord 01.jpg
-

and not _just_ related to deleting stuff, bercause I get this too:

-
Mail Folder/Trash
rsync(68157) malloc: *** error for object 0x8066b8: Non-aligned
pointer being freed
*** set a breakpoint in malloc_error_break to debug
Spool Folder/
Spool Folder/In.temp
rsync(68157) malloc: *** error for object 0x334760: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
-

and so on. This doesn't seem to be affecting my backups at all, but I
thought y'all might like to know about it.  I haven't included my
rsync commands, because I don't think that's what the problem is, but
they're pretty much along the lines of -aNHAXvhtb --fileflages with a
--backup-dir and an --exclude-from and --delete and --fake-super. I
may not need the H.

Thanks.

-- 
W. Oates
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Error messages 3.0.6pre1

2009-04-17 Thread Warren Oates
[sorry if this appears twice -- I'm having trouble with my Gmail filters]

I compiled 3.0.6pre1, including  the crtimes and fileflags patches for
use on Intel OS X 10.5.6, as described by Mr. Bombich (thanks!) here:
http://www.bombich.com/mactips/rsync.html

I want to use 3.0.6 because it seems that this bug:
https://bugzilla.samba.org/show_bug.cgi?id=5365
has been resolved (yay!).


-
[~]$ rsync --version
rsync  version 3.0.6pre1  protocol version 30
Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
   64-bit files, 32-bit inums, 32-bit timestamps, 64-bit long ints,
   socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
   append, ACLs, xattrs, iconv, symtimes, file-flags
-

However, now I'm getting these kinds of messages throughout my output:

-
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard sketch. 01.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard sketch 00.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard 03.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard 02.psd
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard 02.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leonard 01.jpg
rsync(68321) malloc: *** error for object 0x80af80: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
deleting Desktop/PURDY/Lines of the Poet/Leanord 01.jpg
-

and not _just_ related to deleting stuff, bercause I get this too:

-
Mail Folder/Trash
rsync(68157) malloc: *** error for object 0x8066b8: Non-aligned
pointer being freed
*** set a breakpoint in malloc_error_break to debug
Spool Folder/
Spool Folder/In.temp
rsync(68157) malloc: *** error for object 0x334760: Non-aligned
pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug
-

and so on. This doesn't seem to be affecting my backups at all, but I
thought y'all might like to know about it.  I haven't included my
rsync commands, because I don't think that's what the problem is, but
they're pretty much along the lines of -aNHAXvhtb --fileflages with a
--backup-dir and an --exclude-from and --delete and --fake-super. I
may not need the H.

Thanks.

-- 
W. Oates
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


DO NOT REPLY [Bug 3245] improve rsync's error messages to make them clearer

2008-10-02 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3245





--- Comment #1 from [EMAIL PROTECTED]  2008-10-02 21:09 CST ---
Yes, the code 23 message was bad.  It has been improved:

rsync error: some files/attrs were not transferred (see previous errors) (code
23) at main.c(1040) [sender=3.0.4]

Daniel, if you have other specific suggestions, please state them or attach a
patch.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the bug, or are watching the QA contact.
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Newbie can't figure out error messages

2007-01-16 Thread John Jason Jordan
I am trying to use rsync to create a mirror of my Linux laptop (Ubuntu
Dapper amd-64) onto a USB drive hanging on a Windows 2000 desktop over
ethernet. The folder I want to rsync to is /laptop and the USB drive is
mounted at /media/smb using the following:

sudo mount -t smbfs -o username=jcj //Devil4/Linux_Backups /media/smb

Mounting works fine -- the mount command shows the USB drive as mounted.

I have been working on the rsync command for over a day. The following
is what I am using at this point:

sudo rsync -av --delete --exclude=/proc --exclude=/media / /media/smb/laptop

This does copy the files to the /laptop folder on the USB drive. That
is, Windows Explorer sees the files there, so I know I have copied the
files there and not just to the /media/smb mount point. However, I get
a lot of error messages like the following (chosen at random):

rsync: mknod /media/smb/laptop/dev/.static/dev/.static/dev/rfcomm74 failed: 
Operation not permitted (1) rsync: symlink
/media/smb/laptop/dev/.static/dev/.static/dev/sr0 - scd0 failed: Operation 
not permitted (1)

When I say a lot of error messages I mean more error messages than
files actually copied. I selected the above two because all the error
messages related to mknod and symlink.

I haven't been using Linux very long and I don't understand how to fix
this. I have read the man page and I have googled all over, but can't
find anything that explains what to do about these error messages. All
I can find is that (1) means a syntax error, but that doesn't make any
sense if it is a permissions problem.

Can anyone help?
-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: Newbie can't figure out error messages

2007-01-16 Thread Matt McCutchen

On 1/16/07, John Jason Jordan [EMAIL PROTECTED] wrote:

I am trying to use rsync to create a mirror of my Linux laptop (Ubuntu
Dapper amd-64) onto a USB drive hanging on a Windows 2000 desktop over
ethernet.



rsync: mknod /media/smb/laptop/dev/.static/dev/.static/dev/rfcomm74 failed: 
Operation not permitted (1) rsync: symlink
/media/smb/laptop/dev/.static/dev/.static/dev/sr0 - scd0 failed: Operation 
not permitted (1)


The trouble is that some aspects of your Linux laptop's filesystem,
including device nodes and symlinks, cannot be represented on the USB
drive through SMB.  If this is a problem (e.g., if you want to be able
to restore the entire laptop from the USB drive and have it work), I
can think of two options you might try:

(1) Attach the USB drive directly to the laptop, create a Linux
filesystem on the drive (e.g., ext3 or reiserfs), and back up the
laptop to that filesystem with rsync.

(2) Store a tar file of the laptop into the SMB share, in which case
all the Linux-specific metadata is contained in the tar file and no
special help is needed from SMB:
tar -zcf /media/smb/laptop.tar.gz --anchored --exclude=/proc --exclude=/media /

Matt
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


[Bug 3245] New: error messages not precise enough

2005-11-06 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3245

   Summary: error messages not precise enough
   Product: rsync
   Version: 2.6.6
  Platform: x86
OS/Version: Windows XP
Status: NEW
  Severity: normal
  Priority: P3
 Component: core
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
 QAContact: [EMAIL PROTECTED]


Generally speaking, it seems that the structure to report an error is badly 
implemented, and makes the error messages not clear enough.
For example, we might get a Code 23 error, but don't know anything about it. 
This makes misconfigurations difficult to find out and makes the mailing list 
far too buzy providing support to all users who don't know about that or this 
problem.

I think that the code should be a bit rewritten as for the output of the 
messages. Normally we can know if there was a memory problem, a disk problem, 
a file that was missing when doing the copy (and which one) or anything else 
and it would be very helpful to print that out to the user. Also, one 
interesting thing would be to assert errors in the code itself so that we 
could know exactly where in the code the problem happened. The current code 
line report normally just specifies the end of a main procedure merely that 
the exact place of the error.

Regards,
Daniel

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the bug, or are watching the QA contact.
-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


[Bug 3220] list of error messages

2005-10-27 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3220


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




--- Additional Comments From [EMAIL PROTECTED]  2005-10-27 17:29 ---
This is a request for information, not a bug report.  The best place to ask
questions is on the mailing list.

As long as I'm here, I might as well answer:

A usage error means that you got the options wrong or didn't use any at all. 
See the manpage for the full details of how to use rsync, including a brief list
of all the EXIT VALUES.  Also, running rsync --help gives you a quick
command/option summary.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the bug, or are watching the QA contact.
-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


No error messages in rsyncd log in 2.6.1pre-1

2004-04-27 Thread John Van Essen
(As I was composing this, the 2.6.1 release notice on the rsync
 list rolled in.  The quoted source, below, hasn't changed, so
 I'll leave the 'pre-1' references unchanged...)

I have a situation where an error message seems to be sent from
the daemon to the client, but none is logged in the daemon's log.

Daemon is 2.6.1pre-1, with --timeout=3600, light CPU load.

Client is 2.5.5, with --timeout=3600, very heavy CPU load.

The client initiates a pull from the daemon.  I believe the file
list is received by the client pretty quickly.  The client machine
is very busy and it take well over 3600 seconds for it to work its
way down the list and finally get to a file that it needs to sync.
At that point, it errors out.  Here's the final output:


receiving file list ... done
games/empireearth2/
io timeout after 3600 seconds - exiting
rsync error: timeout in data send/receive (code 30) at io.c(85)
games/sacred/
rsync: connection unexpectedly closed (261664 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(150)


I've run into this situation prior to 2.6.1, and as I recall, the
'io timeout' message did not appear (and possibly the line after
it, also).  I recall just the 'connection unexpectedly closed'
message appearing, and the appropriate timeout error message would
be in the rsyncd log.

But now, beyond the initial 'rsync on [module] from [host]' message,
there are no further entries in the rsyncd log for this timeout case.
There should be an error message to indicate what happened, and when.

There was a change to rwrite() that seems to be preventing the error
logging.  This 2.6.1 code:

if (am_server) {
/* Pass it to non-server side, perhaps through our sibling. */
if (msg_fd_out = 0) {
send_msg((enum msgcode)code, buf, len);
return;
}
if (io_multiplex_write((enum msgcode)code, buf, len))
return;
}

will send all errors to the client and none to the log when the
daemon is the server.  That code replaced this code in 2.6.0:

/* first try to pass it off to our sibling */
if (am_server  log_error_fd != -1) {
err_list_add(code, buf, len);
err_list_push();
return;
}

/* next, if we are a server and multiplexing is enabled,
 * pass it to the other side.  */
if (am_server  io_multiplex_write(code, buf, len)) {
return;
}

which had replaced even older code in 2.5.6:

/* first try to pass it off to our sibling */
if (am_server  log_error_fd != -1) {
err_list_add(code, buf, len);
err_list_push();
return;
}

/* next, if we are a server but not in daemon mode, and multiplexing
 *  is enabled, pass it to the other side.  */
if (am_server  !am_daemon  io_multiplex_write(code, buf, len)) {
return;
}

so it looks like there's a missing !am_daemon in the newer code,
and this problem probably existed in 2.6.0, but I hadn't run into
this timeout problem in the past few months to notice it.

In any case, shouldn't errors (FERROR) *always* be logged via logit()
if running as a daemon even if they are also sent to the sender?
I'd sure like to see that.  So there's perhaps more to be adjusted
here than just adding back a !am_daemon test?

Also - I'd sure like to see a message in the rsyncd log when the
file list transfer has been completed.  That would help determine
at what stage things are failing (and how long it took for the
file transfer to complete, in case that helps).
-- 
John Van Essen  Univ of MN Alumnus  [EMAIL PROTECTED]

-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


Re: No error messages in rsyncd log in 2.6.1pre-1

2004-04-27 Thread Wayne Davison
On Tue, Apr 27, 2004 at 05:15:25AM -0500, John Van Essen wrote:
 There was a change to rwrite() that seems to be preventing the error
 logging.

Yes, you're right -- 2.6.0 changed this to make more errors go to the
user and fewer to the log file.  Neither the old behavior nor the new is
really the right one going forward, though, so the future code should
really be modified to allow the calling routine to tell us if a message
should be logged to both the user and the log file, or if it is so
sensitive that it should only go to the log file.

If you want to make rsync behave as it did prior to 2.6.0, you could
apply the appended patch.  I have not checked this in, though.

..wayne..
--- log.c   20 Jan 2004 05:15:14 -  1.71
+++ log.c   27 Apr 2004 20:15:06 -
@@ -182,7 +182,8 @@ void rwrite(enum logcode code, char *buf
send_msg((enum msgcode)code, buf, len);
return;
}
-   if (io_multiplex_write((enum msgcode)code, buf, len))
+   if (!am_daemon
+io_multiplex_write((enum msgcode)code, buf, len))
return;
}
 
-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Error Messages

2002-05-31 Thread Scott Sipe

Hi, I'm using rsync to backup files from a file server at an office to a
remote location.  The office connection is a DSL line (fairly slow--40KB/s
avg) that is NAT'd through an OpenBSD 3.1 box.  The rsync server is behind
the NAT box with a private address of 10.1.1.3.  Using pf I expose the rsync
server with:

# Rsync
rdr on fxp1 from any to any port 873 - 10.1.1.3 port 873

On the remote side, the connection is a cable modem (capable of downloading
much faster than the office can send).  The home computer is behind a
Netgear cablemodem NAT router, wit a private address of 192.168.0.103.  (So
both ends are NAT'd, if this makes a difference).

Both sides are running FreeBSD 4.5 (one is running 4.6 prerelease--since the
final version is due out within the next couiple days I would expect it to
be fairly stable), with the latest version of the rsync port (rsync-2.5.5_1
is the port number).

First question--on the server logs it complains: (it seems to spit that out
everytime I trigger a remote rsync)
May 31 20:51:00 boudicca /kernel: May 31 20:51:00 boudicca rsyncd[75171]:
/etc/pwd.db: No such file or directory

This doesn't seem to make a difference though.

Secondly, I can rarely finish synching.  I tried for about a week to sink
one share (~9GB of data in total) and never was able to get more than 1GB.
Eventually I took the remote rsync client physically into the office and
synched on the local network fine--no errors, all 9GB done in about 20
minutes or so iirc.  I was able to synch ok for 2 days from the remote
location and now got more errors.  The output on the client looks like this:

start
receiving file list ... done
Z2/DATA/
Z2/DATA/FILESALE.TXT
rsync: error writing 4092 unbuffered bytes - exiting: Broken pipe
rsync: read error: Operation timed out
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
rsync error: received SIGUSR1 or SIGINT (code 20) at main.c(784)
/end

FILESAVE.TXT is an 11MB file.

I have the client automatically email when the synch finishes with the
output.  On the server side the error is:
May 31 20:59:37 boudicca rsyncd[75171]: rsync: error writing 4096 unbuffered
bytes - exiting: B
roken pipe
May 31 20:59:37 boudicca rsyncd[75171]: rsync error: error in rsync protocol
data stream (code
12) at io.c(463)

The server config is:
start
max connections = 10
syslog facility = local3
secrets file = /etc/rsync.secrets
read only = yes
auth users = scott
list = yes

[UserDrive]
comment = Userdrive
path = /userdrive
[Cats]
comment = Cats Files
path = /cats
/end

the command run from the client is:
/usr/local/bin/rsync -apogtv --delete --stats
[EMAIL PROTECTED]::Cats --password-file
/etc/rsync.password /cats/ 21 | /usr/bin/mail -s Rsync Report (Cats)
[EMAIL PROTECTED]

I had read somewhere that verbose might screw things up, but it still
doesn't complete even on quiet mode.

Some more info, the two shares I'm trying to synch are being served at the
office with Netatalk and Samba.  The cats share for which I posted logs
above is only samba, no netatalk.

So that's my problem.  I hope I gave enough information to give some idea of
what is going on.

thanks,
Scott Sipe
[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



Error messages

2002-05-06 Thread Jennifer Lu



Hi,

We ran 2.5.5 rsync version between Sun-OS 5.8 and Sun-OS 5.6, and
kept getting error messages -

partial transfer (code 23) at main.c(925), 

The job completed, but with this error? Can you please help?

Thanks,
Jennifer


-- 
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 messages

2002-03-08 Thread Dave Dykstra

Don't use rsync 2.5.2, it's got some serious problems.  They're fixed in
the 2.5.3pre* versions in the preview directory on the rsync sources
download site.  Unfortunately we don't make binaries except for released
versions releases though, sorry.

The Solaris251 binaries in the rsync binaries area should work on all
SunOS 5.5.1 and later, yes.

- Dave Dykstra


On Tue, Mar 05, 2002 at 01:55:58PM -0800, Jennifer Lu wrote:
 
 
 
 Hi,
 
 We got the following error messages when we ran rsync 2.5.2
 from Solaris-5.5.1 to Solaris-5.8.
 
 vl121909/jagcdms_ch+_diags/sys/sys_l/ch_sys/rtl/systop.v
 vl121909/jagcdms_ch+_diags/sys/sys_l/ch_sys/rtl/sysup_esat.v
 vl121909/jagcdms_ch+_diags/sys/sys_l/ch_sys/rtl/upesat_defines.h
 wrote 63878001383 bytes  read 1529124 bytes  1246928.64 bytes/sec
 total size is 148182624008  speedup is 2.32
 rsync error: partial transfer (code 23) at main.c(576)
 
 I have downloaded rsync-2.3.2.tar.gz  rsync-2.5.2.Solaris251.sparc.tar.gz, 
 is rsync-2.5.2.Solaris251.sparc.tar.gz mainly for Solaris5.5.1.1? 
 This file already has rsync binary, so I don't need to re-compile it, right?
 
 Thanks for the help,
 Jennifer
 
 
 -- 
 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



List of rsync output / error messages

2002-02-06 Thread Joseph Annino

Is there a good place to get information about the list of all possible
output and error messages rsync generates?  Or should I just muck around the
source code (which I haven't looked at yet) and find them?

I am doing something where I would like to parse rsync's output using Perl
into a set of data structures.  I already have something that works under
normal conditions.  Eventually I'd like to use that data as part of building
a Perl/Tk interface.  Of course to parse the output successfully, I need to
know all the possibilities as surprises can throw things out of whack.

And this is just an idea, but ways to make rsync's output more easily
parseable, and more verbose in terms to reporting information that would be
useful for say making a progress bar would be nice to discuss.

Thanks.


-- 
Joseph Annino Consulting - Perl, PHP, MySQL, Oracle, etc.
[EMAIL PROTECTED] - http://www.jannino.com





Re: List of rsync output / error messages

2002-02-06 Thread Alberto Accomazzi


Joseph,

check out the header file errcode.h in the rsync distribution.
That file and the structure found in log.c map the system exit codes to 
the error messages you refer to, so the best way to programmatically
catch errors is simply to check the exit status returned by rsync.

-- Alberto


In message [EMAIL PROTECTED], Joseph Annino writes:

 Is there a good place to get information about the list of all possible
 output and error messages rsync generates?  Or should I just muck around the
 source code (which I haven't looked at yet) and find them?
 
 I am doing something where I would like to parse rsync's output using Perl
 into a set of data structures.  I already have something that works under
 normal conditions.  Eventually I'd like to use that data as part of building
 a Perl/Tk interface.  Of course to parse the output successfully, I need to
 know all the possibilities as surprises can throw things out of whack.
 
 And this is just an idea, but ways to make rsync's output more easily
 parseable, and more verbose in terms to reporting information that would be
 useful for say making a progress bar would be nice to discuss.
 
 Thanks.
 
 
 -- 
 Joseph Annino Consulting - Perl, PHP, MySQL, Oracle, etc.
 [EMAIL PROTECTED] - http://www.jannino.com
 




Alberto Accomazzi  mailto:[EMAIL PROTECTED]
NASA Astrophysics Data System  http://adsabs.harvard.edu
Harvard-Smithsonian Center for Astrophysicshttp://cfawww.harvard.edu
60 Garden Street, MS 83, Cambridge, MA 02138 USA   





no error messages on I/O errors

2001-11-03 Thread Ian! D. Allen [NCFreeNet]

rsync-2.4.6-2mdk

I ran an rsync into a file system that filled up.  I got no error message
out of rsync - it just stopped and exited sliently.  I stuck an fprintf
into the receiving code and verified that the proper error was being
generated - it just never gets printed by the rsync sending process.

I submitted a bug report about it; but, I can't believe that other
people haven't had this bite them.

Also, shouldn't rsync continue with the other files that *do* fit into
the destination, rather than dying on the first one that doesn't fit?
Perhaps we need an --ignore-errors-even-further option...

-- 
-IAN!  Ian! D. Allen   Ottawa, Ontario, Canada   [EMAIL PROTECTED]
   Home Page on the Ottawa FreeNet: http://www.ncf.ca/~aa610/
   College professor at: http://www.algonquincollege.com/~alleni/
   Board Member, TeleCommunities CANADA  http://www.tc.ca/