FUSE-based single file backing store via Amazon S3
http://s3backer.googlecode.com/
s3backer is a filesystem that contains a single file backed by the Amazon
Simple Storage Service (Amazon S3). As a filesystem, it is very simple:
it provides a single normal file having a fixed size. Underneath, the
file is divided up into blocks, and the content of each block is stored
in a unique Amazon S3 object. In other words, what s3backer provides is
really more like an S3-backed virtual hard disk device, rather than a
filesystem.
In typical usage, a `normal' filesystem is mounted on top of the file
exported by the s3backer filesystem using a loopback mount (or disk image
mount on Mac OS X).
- Developed at filesystems
-
3
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory/s3backer && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| s3backer-2.1.0.tar.gz | 0000502438 491 KB | |
| s3backer.changes | 0000010666 10.4 KB | |
| s3backer.spec | 0000003205 3.13 KB |
Revision 27 (latest revision is 29)
Ana Guerrero (anag+factory)
accepted
request 1113218
from
Archie Cobbs (archie172)
(revision 27)
- Upgrade to release 2.1.0 + Avoid sending an empty Accept-Encoding header (issue #208) + Use fallocate(FALLOC_FL_PUNCH_HOLE) for empty disk cache blocks (issue #200) + Made sync(1) work on s3backer file to flush cached data (issue #197) + Fixed bug where s3b_compress=deflate NDB flag would fail (issue #195) + Fixed bug in zero cache "current_cache_size" stats value (issue #204) + Reuse cURL handles after normal HTTP error codes (issue #199) + Run modprobe(8) if needed when starting with the --nbd flag (issue #203) + Use newer OpenSSL 3.0 API functions when available
Comments 0