Bug 11013 - rsync hangs
Summary: rsync hangs
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rsync
Version: 6.2
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-04-24 13:19 UTC by wangna
Modified: 2008-05-01 15:37 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2000-04-24 14:43:53 UTC


Attachments (Terms of Use)

Description wangna 2000-04-24 13:19:42 UTC
When I upgraded from Red Hat 6.1 to 6.2, rsync started hanging.

Client (tage): Dell Inspiron 3500 notebook, 128Mb RAM, Red Hat 6.2.
Server (eva): 500MHz Pentium II, 256Mb RAM, Red Hat 5.2.
Ran rsync on the client with the command:

rsync --verbose --verbose --verbose --archive --delete --force --stats
--exclude=/home/howard/.netscape/cache/ --exclude=/home/howard/from-eva/
--exclude=/proc/ --exclude=/tmp/ --exclude=lost+found/ / eva:/r4/tage

This produced a lot of output and transferred about 300Mb to
the server.  Then output stopped in the middle of a line:
   ...
   make_file(home/pk/.gnome/Gnumeric)
   make_file(home/pk/.gnome/Terminal)
   make_file(home/pk/.gnome/gm
There was no activity for several minutes.  ps on the client
showed
  883 ttyp0    S      0:12 rsync --verbose --verbose --verbose --archive
--delete --force --stats --
  884 ttyp0    S      0:00 rsh eva rsync --server -vvvlogDtpr --delete
--force . /r4/tage
  885 ttyp0    S      0:01 rsh eva rsync --server -vvvlogDtpr --delete
--force . /r4/tage
with no changes to the times.  df on the server showed no
changes in file system disk usage.  I could interrupt (^C) the
rsync command on the client.

This is repeatable, although the hang does not occur at the
same place each time.

On the client I downgraded to rsync 2.3.1-2 from the Red Hat
6.1 CD.  This works fine.

Comment 1 Bill Nottingham 2000-04-24 14:43:59 UTC
Please grab the latest rsync from rawhide (ftp://ftp.redhat.com/pub/rawhide/)
this should fix your problem.


Note You need to log in before you can comment on or make changes to this bug.