Release Notes: Apart from many bugfixes and performance improvements, this release also introduces a couple of new features and an improved user's guide. The file system metadata is now only uploaded if there have been any changes. S3QL now supports several parallel compression and encryption threads. S3QL now supports "immutable directories".
Release Notes: Cycling of metadata backups when using the local backend now takes much less time. It is no longer required that S3QL and Python APSW be linked to the same SQLite shared library. In mount.s3ql, a crash when using --metadata-upload-interval 0 was fixed. Instead of completely unmounting the file system (and leaving the mount point inaccessible) when backend data is missing or corrupted, S3QL now returns an error and switches to read-only operation.
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.