samba-bugs at samba.org
2009-Dec-04 10:00 UTC
DO NOT REPLY [Bug 6965] New: truncated files and exit code 23
https://bugzilla.samba.org/show_bug.cgi?id=6965 Summary: truncated files and exit code 23 Product: rsync Version: 3.0.4 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: martin.pihlak at gmail.com QAContact: rsync-qa at samba.org While backing up an active PostgreSQL database, I occasionally get exit code 23 from rsync, accompanied by a error messages: rsync: read errors mapping "/data/postgresql/8.3/main/base/144458723/1009564226": No data available (61) rsync error: some files could not be transferred (code 23) at main.c(1058) [sender=3.0.3] As indicated by http://lists.samba.org/archive/rsync/2009-November/024133.html this is caused by the file being truncated while being read by rsync. On an active database this is actually a normal condition, as files are created, deleted and truncated all the time. Unfortunately the code 23 cannot just be ignored, as it also may indicate that there was an actual "real" IO error during the backup. And without reading rsync output there is no way to tell. So the proposal is to avoid generating ENODATA for truncated files and treat them similarly to vanished files. -- 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.
samba-bugs at samba.org
2009-Dec-14 07:42 UTC
DO NOT REPLY [Bug 6965] Avoid code 23 when source file is concurrently truncated
https://bugzilla.samba.org/show_bug.cgi?id=6965 matt at mattmccutchen.net changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|truncated files and exit |Avoid code 23 when source |code 23 |file is concurrently | |truncated ------- Comment #1 from matt at mattmccutchen.net 2009-12-14 01:42 CST ------- Indeed. This is probably one of many kinds of concurrent modification to the source that rsync handles ungracefully. In general, when different system calls return inconsistent results, that could indicate either a concurrent modification or filesystem misbehavior. The downside to always assuming concurrent modification is that we miss the opportunity to report filesystem misbehavior if it happens. One example is the Cygwin "file has vanished" error with foreign characters in filenames ( http://lists.samba.org/archive/rsync/2008-January/019696.html ). -- 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.
Maybe Matching Threads
- DO NOT REPLY [Bug 7956] New: Don't error when attempting to delete a non-existent default ACL
- DO NOT REPLY [Bug 6025] New: 0 files to consider should not return code 23
- DO NOT REPLY [Bug 5894] New: Incompatible library version
- DO NOT REPLY [Bug 7109] New: Need to define NO_SYMLINK_XATTR on Linux
- DO NOT REPLY [Bug 6752] New: --force option doesn't work as expected/documented