4 ms·

Is this triggered under certain workloads, or has it been chewing data for everyone, and how much?

• csdvrx 3y ago
  > Is this triggered under certain workloads, or has it been chewing data for everyone, and how much? Unless you are checksumming your files through a daemon run on a schedule (IDS style) AND manually review the results every now and then, you can't know.
  • uselpa 3y ago
    If you have versioned backups, you can diff against update_day-1 without an additional tool.
    • csdvrx 3y ago
      I have versioned backups for a few months. Most people don't and can't (it requires a lot of storage) Even if they have them, the diffing needs to be done. Given the past problems with ZFS, I think I'll write a summarizer, that creates a database of metadata for each backup: it will be small to keep around, and may be use more easily to determine which backup contains the uncorrupted file.
      • uselpa 3y ago
        I use borgbackup so the storage requirements are fairly low if the data does not change too much (which is my case). Also diffs are just a « borg diff » away.
• o11c 3y ago
  It appears to require O_DIRECT, which is notoriously buggy and no sane program should ever use.
  • spyc 3y ago
    Could you share your source on how/when/if O_DIRECT is required? Have a link?
    • fulafel 3y ago
      It's in this HN submission's link. It could be that O_SYNC is also needed.