Dear all, I am pleased to announce a new release of S3QL, version [PASTE VERSION].
>From the changelog:
2021-06-03, S3QL 3.7.3
* Fixed a DATA CORRUPTION bug in fsck.s3ql that caused the recorded size of
uploaded
dirty blocks to be rounded up to the next multiple of 512 bytes,
effectively appending
up to 512 zero-bytes to the end of affected files.
This problem was introduced in version 3.4.1 (released 2020-05-08) as part
of a
seemingly very minor improvement to cache usage calculation.
You can tell that a file has (likely) been affected from fsck.s3ql messages
of the
form:
WARNING: Writing dirty block <X> of inode <Y>
followed later by:
WARNING: Size of inode <Y> (<path_to_file>) does not agree with number of
blocks, \
setting from <reasonable_size> to <size rounded to next multiple of 512)
The following people have contributed code to this release:
Nikolaus Rath <[email protected]>
(The full list of contributors is available in the AUTHORS file).
The release is available for download from
https://github.com/s3ql/s3ql/releases
Please report any bugs on the mailing list ([email protected]) or
the issue tracker (https://github.com/s3ql/s3ql/issues).
Best,
-Nikolaus
--
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/s3ql/87czt27mxu.fsf%40vostro.rath.org.
signature.asc
Description: PGP signature
