Public bug reported:
There is a bug in src/s3ql/_deltadump.pyx, which repositions a file descriptor
associated with a FILE* stream without first calling
fflush(). When using eglibc 2.17, this means that s3ql will store malformed
metadata that cannot be loaded again. The problem is made worse because this
affects only the metadata uploaded to the remote server, but not the locally
cached copy. So unless the user explicitly tests reloading the metadata from
the server, the corruption will not show up until it's too late.
** Affects: s3ql (Ubuntu)
Importance: Undecided
Status: New
** Affects: s3ql (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #701350
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701350
** Also affects: s3ql (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701350
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1179281
Title:
Data corruption with eglibc 2.17
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1179281/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
