RE: rsync process never quits! BUG? PROBLEM?

[Polyanovskyi, Sasha]

Title: Message




OK, I 
think this is an RSYNC bug!
When I 
start a single rsync process on the source machine, everything works fine: 
on the destination machine the listening daemon exits after the operation 
completes. When I start more than one rsync process on the source machine, 
here is what happens:

  on some of the destination 
  machines not just one rsync daemon, but two rsync.exe processes become 
  running (even though only one of several 
  parallel rsync processes from the source machine deals with such 
  a destination machine)
  after 
  the operation completes all the rsync.exe processes on such destination machines remain running 
forever!
It seems as if parallel RSYNCs on the source machine 
get confused with one another, sending unnecessary requests to 
daemons of some destinations machines and never closing the connections 
from those requests
 
Please 
read below for more details if interested
 

  
  -Original Message-From: Polyanovskyi, 
  Sasha [mailto:[EMAIL PROTECTED] Sent: Monday, August 
  16, 2004 5:11 PMTo: '[EMAIL PROTECTED]'Subject: 
  rsync process never quits!
  Hi, people. Please help! I run rsync under inetd in Cygwin environment on Windows 
  2000. I start several rsync processes each in a separate thread to sync a 
  directory on my machine and a corresponding directory on another computer, 
  e.g. three RSYNCs at the same time:
  
directories C:\aaa on 192.168.1.100 and C:\bbb 
on 192.168.50.20 
directories C:\aaa on 192.168.1.100 and C:\bbb 
on 192.168.50.21 
directories C:\aaa on 192.168.1.100 and C:\bbb 
on 192.168.1.100 
  Note that the sync could be between two directories 
  on my machine... 
  The command I use has the following 
  structure:  rsync OPTIONS SRC [EMAIL PROTECTED]::DEST (even when both SRC and DST 
  are the same machine, I access DST with specifying its IP address).
  Everything works technically, but here is the 
  problem: if I start more than one thread at a time with RSYNC process, it 
  seemd to get confused on the destination machine. After everything is 
  completed I get a number of rsync.exe processes on the destination machine 
  running forever and never exiting! I think they are daemons accepting 
  connections, but I am not too sure. Can anyone please tell me how to get rid 
  of them. I certainly can write a program that would run on every remote 
  machine and kill the RSYNCs that hang in the process list for more than 
   minutes, but surely this is not a very elegant solution 
  :-)
  Thanks in advance 

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

testing rsync 2.6.3pre1

[Wayne Davison]

I announced the release of 2.6.3pre1 on the rsync-announce mailing list
back on the 12th.  I was thinking at the time that this email would get
seen by those on the regular rsync list, but I forgot that this is not
how the rsync lists are setup.  For those that missed it, here is the
text of the announcement:

--

I have released rsync 2.6.3pre1 -- the first pre-release version of
2.6.3.  Please help out with the testing so that the code gets a good
workout before 2.6.3 is released.  Thanks!

To see what has changed, read this text file:

http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.3pre1-NEWS

To download a copy, use one of these links:

http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.3pre1.tar.gz
http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.3pre1.tar.gz.asc

http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.2-2.6.3pre1.diffs.gz
http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.2-2.6.3pre1.diffs.gz.asc

The diffs no longer include the "patches" subdir (since including them
makes the diffs double in size).  If you want an updated set of patches
without grabbing the tar file, you can use rsync to update the patches
dir in your rsync source using this command:

rsync -av --delete rsync://rsync.samba.org/ftp/unpacked/rsync/patches ~/src/rsync/

--

I'd appreciate it if people would let me know about any testing they do,
even if it's just to say that things are working fine.

..wayne..
-- 
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: Mac OS X HFS+ metadata patch, take 2

[Gregory Brauer]

D Andrew Reynhout wrote:
The diff and a binary (and a fuller explanation) can be found at:
http://www.quesera.com/~reynhout/misc/rsync-hfsmode-patch
This is excellent!  It should vastly speed up our Linux to Mac
rsync transfers over any of the other available alternatives.
Two questions:
Do you have to have rsync-hfsmode on both the sending and
receiving machines, or will rsync-hfsmode work properly with
a standard rsync install in one direction or the other?
Is there any chance of this being folded into the standard
rsync CVS?
Greg
--
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: Mac OS X HFS+ metadata patch, take 2

[Wayne Davison]

On Mon, Aug 16, 2004 at 12:49:17AM -0400, D Andrew Reynhout wrote:
> The diff and a binary (and a fuller explanation) can be found at:
> http://www.quesera.com/~reynhout/misc/rsync-hfsmode-patch

Please don't use -b when creating a diff -- it makes a patch that does
not recreate the modified source.  I'd be glad to put this into the
patches dir for the next release, but it will need to be updated to
apply to 2.6.3pre1 first.

..wayne..
-- 
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: [RSYNC] Mac OS X HFS+ metadata patch, take 2

[Ashley M. Kirchner]

D Andrew Reynhout wrote:
Several months ago, I posted my first pass at a patch to transfer
Mac OS X HFS+ metadata (resource forks and Finder metadata) to
non-HFS+ filesystems (Linux, Solaris, etc).
   Here's a different take, one that's been causing me problems all 
over, and I can't figure out if it's rsync, or samba, or some other 
force causing the problems.  First, the setup:

   The bulk of the company works on Win32 machines, except our digital 
department, who are all using Macs.  Therefor, we have a few large Win2K 
servers who act as file servers on the network for anyone to use.  This 
works well; the folks on Win32 machines can see/use them and the folks 
in Digi can also see/use them.  Those guys use both OS 9 as well as OS X 
machines.

   Here's what I want to do: they purchased a new Win2K server and 
loaded it up with large drives, to be used as backups for the other 
servers around the building.  Basically what they want is a (semi) 
mirror copy of what the other servers hold, in case of a server failure, 
so they can simply re-map their share to the backup server and continue 
working while I fix the failed one (the data would be no more than 48 
hours old since backups would only run either every night or every other 
night.)

   Sounds simple enough, right?  So, here's what I thought of doing: 
take a free linux box I had sitting in a closet, and use it to act as a 
sort of backup manager.  Let's assume we have Server-A with Drive1 and 
Drive2 on it.  Now we have BackupServer with Drive1 and Drive2 on it.  
On the linux box, I do an smbmount to get Server-A:Drive1 mounted, and 
the same for BackupServer:Drive1.  Then I run rsync on those drives.  
And this is where the problems start.  I posted this message to the 
Samba-Tech list as well, so I'm just going to quote the archived version 
here:

   http://lists.samba.org/archive/samba-technical/2004-August/036630.html
   I'd like to think it's samba not being able to read those files, but 
from what I read here today, it seems maybe rsync is also having 
problems.  So I'm fishing for possible ideas here.

   Now, I will also admit, this may not be the ideal setup.  Perhaps I 
should just stick to xcopy on the backup server and let it do it's 
thing.  I don't know.  What I DO know is that we want to stay as far 
away as we can from having to buy some expensive, network backup 
software.  We've had our share of bad luck with them (they don't always 
grab everything, which has come back and bit us hard in the past.)

   If anyone has any brilliant ideas, I'm all ears.
--
W | I haven't lost my mind; it's backed up on tape somewhere.
 +
 Ashley M. Kirchner    .   303.442.6410 x130
 IT Director / SysAdmin / WebSmith . 800.441.3873 x130
 Photo Craft Laboratories, Inc.. 3550 Arapahoe Ave. #6
 http://www.pcraft.com . .  ..   Boulder, CO 80303, U.S.A.

--
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: Mac OS X HFS+ metadata patch, take 2

[Kevin Alexander Boyd]

Here's another method for HFS+ rsyncs to non-HFS+ filesystems - the files
can be synced and restored without using RsyncX:

http://xnews.soad.umich.edu/RsyncX_Forums/index.php?topic=33.0

There have been varying degrees of happiness with this method.  It's not
perfect, just another alternative method.

Kevin Boyd
OS X Deployment Coordinator
Sys Adm UMIT Contract Services


On Mon, 16 Aug 2004, D Andrew Reynhout wrote:

> Date: Mon, 16 Aug 2004 00:49:17 -0400
> From: D Andrew Reynhout <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Mac OS X HFS+ metadata patch, take 2
>
>
> Hi.
>
> Several months ago, I posted my first pass at a patch to transfer
> Mac OS X HFS+ metadata (resource forks and Finder metadata) to
> non-HFS+ filesystems (Linux, Solaris, etc).
>
> I finally got a chance to update the patch to reflect suggestions
> offered on the list.  Thanks for the ideas, this version should be
> a big improvement.
>
> The diff and a binary (and a fuller explanation) can be found at:
> http://www.quesera.com/~reynhout/misc/rsync-hfsmode-patch
>
> The current patch is against rsync-2.6.2.  It still works with the
> standard build of rsync on the receiving side, so only the sender
> needs to be patched.
>
> For a single HFS+ file, there will be between one and three files
> transferred to the destination filesystem:
>
>- : The regular file (data fork)
>- ._: The resource fork of , iff non-empty.
>- .__metadata: Type and Creator and Finder flags
> for , iff non-null.
>
> Any suggestions on a naming scheme for the metadata file that
> would minimize the risk of collisions?
>
> Any feedback would be appreciated.
>
> Thanks,
> Andrew
> [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
>
-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

rsync process never quits!

[Polyanovskyi, Sasha]

Title: rsync process never quits!





Hi, people. Please help!
I run rsync under inetd in Cygwin environment on Windows 2000. I start several rsync processes each in a separate thread to sync a directory on my machine and a corresponding directory on another computer, e.g. three RSYNCs at the same time:

directories C:\aaa on 192.168.1.100 and C:\bbb on 192.168.50.20
directories C:\aaa on 192.168.1.100 and C:\bbb on 192.168.50.21
directories C:\aaa on 192.168.1.100 and C:\bbb on 192.168.1.100

Note that the sync could be between two directories on my machine...


The command I use has the following structure:  rsync OPTIONS SRC [EMAIL PROTECTED]::DEST (even when both SRC and DST are the same machine, I access DST with specifying its IP address).

Everything works technically, but here is the problem: if I start more than one thread at a time with RSYNC process, it seemd to get confused on the destination machine. After everything is completed I get a number of rsync.exe processes on the destination machine running forever and never exiting! I think they are daemons accepting connections, but I am not too sure. Can anyone please tell me how to get rid of them. I certainly can write a program that would run on every remote machine and kill the RSYNCs that hang in the process list for more than  minutes, but surely this is not a very elegant solution :-)

Thanks in advance



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