That is a very important thing to mention when people do s3ql seen a corrupt cache due to a bad local storage (bitrot, corruption,...) can lead to the loss of data.
Inside the posix file system of s3ql of course you can protect files with parity (par2) But whatabout the metadata and data of s3ql? Do you provide some parity there? If not, can that be extended by s3qlcmd so in a very worse case scenaria, when metadata and data of the s3ql files happens, it can recover? Op donderdag 9 september 2021 om 10:49:11 UTC+2 schreef [email protected]: > On Sep 09 2021, Amos T <[email protected]> wrote: > > In fact what happens if the cache got corrupted? how does s3ql detects > > corrupted cached files? Suppose I put this on a single drive, not on > raid, > > and cache gets corrupted. > > S3QL does not detect corruption on the cache. It would just upload/use > the corrupted data. You're expected to put the cache on a sufficiently > reliable filesystem. > > > So are inodes stable in S3QL ? > > Yes. A files inode never changes, no matter if it's cached or not, or > remounted. > > 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/1bff7b79-760c-460b-b8c3-75cfb6baccean%40googlegroups.com.
