Bug 59013
Summary: | Sync not done properly through ssh | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Matthias Saou <matthias.saou> |
Component: | rsync | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED DUPLICATE | QA Contact: | Aaron Brown <abrown> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | CC: | billc, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-01-29 11:50:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Matthias Saou
2002-01-29 10:04:08 UTC
Ran from a client to a server both running rsync-2.4.6-8 : receiving file list ... done enigma/lbreakout2/ enigma/lbreakout2/lbreakout2-2.2-fr1.i386.rpm Warning: unexpected read size of 0 in map_ptr Warning: unexpected read size of 0 in map_ptr 1114516 (100%) enigma/lbreakout2/lbreakout2-2.2-fr1.src.rpm Warning: unexpected read size of 0 in map_ptr Warning: unexpected read size of 0 in map_ptr 1154599 (100%) enigma/lbreakout2/ wrote 19592 bytes read 2251167 bytes 57487.57 bytes/sec total size is 308556699 speedup is 135.88 After downgrading the server's rpm to rsync-2.4.6-5, it works fine but re-downloads the files (they were probably corrupted after the first download!) : receiving file list ... done enigma/lbreakout2/lbreakout2-2.2-fr1.i386.rpm 1114516 (100%) enigma/lbreakout2/lbreakout2-2.2-fr1.src.rpm 1154599 (100%) enigma/lbreakout2/ wrote 38498 bytes read 1131001 bytes 39644.03 bytes/sec total size is 308556699 speedup is 263.84 I'm having similar problems running the updated rsync over ssh. In one direction I get: unexpected EOF in read_timeout and the transfer fails. In the other direction I get a segmentation fault and the transfer fails. FYI: this isn't only affecting SSH-based transfers. |