We use the boring combo of cassandra snapshots + tar to backup our cassandra nodes; every once in a while, we'll notice tar failing with the following:
tar: data/addresses/addresses-eb0196100b7d11ec852b1541747d640a/snapshots/backup20220318183708/nb-167-big-Data.db: file changed as we read it I find this a bit perplexing; what would cause an sstable inside a snapshot to change? The only thing I can think of is an incremental repair changing the "repaired_at" flag on the sstable, but it seems like that should "un-share" the hardlinked sstable rather than running the risk of mutating a snapshot. James Brown Cassandra admin @ easypost.com
