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.
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.
Release Notes: The s3s, s3cs, and gss backends have been removed. Use the new --ssl option together with the s3, s3c, and gs backends instead. S3QL no longer keeps track of consistency guarantees for the different backends. The increasing number of different storage providers offering different regions, redundancy, and availability levels makes this no longer feasible. The User's Guide contains a new section, "Important Rules to Avoid Losing Data". Reading it is strongly recommended.
Release Notes: This release makes file times no longer change when changing the system time zone, fixes and improves contrib/benchmark.p, fixes the "Too many chained redirections" bug, retries on 5xx server errors, and adds experimental native support for OpenStack/SWIFT servers and experimental proxy support.
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.
Release Notes: Metadata is now stored in a custom, delta-encoded binary format, and inodes are assigned sequentially and not reused. This makes S3QL fully NFS-compatible. s3qlcp now also copies extended attributes and no longer generates incorrect block reference counts when copying a file which has identical blocks. This release eliminates a race condition in s3qlcp. When copying a file with s3qlcp immediately after it was modified or created, it was possible that s3qlcp would copy the new file attributes but the old data blocks.