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: way...@samba.org
ReportedBy: martin.pih...@gmail.com
QAContact: rsync...@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.
--
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
