Version 1.8 of S3QL
Release Notes: A "ValueError: Can't dump NULL values" crash when file system metadata was uploaded during heavy file system activity was fixed. s3qlcp and directory listing performance for very large directories were improved. An rm performance regression was fixed. --blocksize was renamed to --max-obj-size. Some crashes that happened under heavily concurrent file system usage were fixed. python-llfuse 0.37 is now used.
Other releases
Release Notes: Reduced CPU consumption when S3QL is idle. This release automatically retries requests when S3 reports an "internal error" (this functionality was accidentally broken in 1.13). It fixes a hang when using s3qlrm to delete a directory with a very large number of sub-directories.
Release Notes: This release fixes a bug that caused malformed metadata to be written out when using recent eglibc versions. It fixes issues when trying to access a directory at the root of the filesystem that has recently been removed with s3qlrm. Ostensible ACL support has been removed. This release better handles buckets with invalid DNS names. It will retry if DNS is not available.
Release Notes: The file system is now more verbose about how to remedy the situation when attempting to upgrade file systems needing fsck. fsck now detects and fixes directory entries which do not have an entry type stored in their mode field. There were various small bugfixes and code improvements.
Release Notes: This release fixes a crash when using the S3 backend (regression introduced in release 1.11), increases the minimum reported filesystem size to 1 TB, and works around a df bug so size is reported properly.
Release Notes: Metadata about stored objects is now split into multiple fields, so no field is longer than 256 bytes. (This makes S3QL compatible with a wider range of storage providers.) The SWIFT backend now retries if it receives 5xx error codes from the remote server, and no longer fails when attempting to upload data with an expired auth token.
