A data corruption bug in OpenZFS?

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • zfs

    OpenZFS on Linux and FreeBSD

  • https://github.com/openzfs/zfs/issues/15526#issuecomment-181...

    > zpool get all tank | grep bclone

    > kc3000 bcloneused 442M

    > kc3000 bclonesaved 1.42G

    > kc3000 bcloneratio 4.30x

    > My understanding is this: If the result is 0 for both bcloneused and bclonesaved then it's safe to say that you don't have silent corruption.

  • bmap-tools

    Discontinued BMAP Tools

  • > But I recall reading elsewhere a discussion about some userspace program which did depend on holes being present in the filesystem as actual holes (visible to SEEK_HOLE and so on) and not as runs of zeros.

    > treatment of on-disk segments as "what was written by programs" can cause areas of 0 to not be written by bmaptool copy

    https://github.com/intel/bmap-tools/issues/75

    IMO, the issue here isn't filesystem or zfs behavior, it's that bmap-tool wants an extra "don't care bit" per block, which filesystems (traditionally) don't track, and programs interacting with filesystem don't expect to exist.

    Some of the comments I've made in this issue describe options to make things better.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • bcachefs

  • I'm keeping an eye on it but it's not there yet e.g. https://github.com/koverstreet/bcachefs/issues/619#issuecomm...

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts