Joachim Wagner
Joachim Wagner
Issue #451 mentions: > Currently it reads one mirror, and if that fails [...] it reads the other mirrors in turn. It doesn't issue reads on both copies at once...
There is a mount option `fatal_errors=action` but - no explanation what errors are considered fatal - no corresponding option for non-fatal errors - no action "report-and-continue" I also didn't find...
Users are trying to force SSDs to store `dup` copies twice by adding an encryption layer such as LUKS below btrfs. https://github.com/kdave/btrfs-progs/issues/319#issuecomment-1069286104 points out that this setup may still not...
## Problem Description Reading in issue #319 that the 2 blocks created by `dup` for a single block of metadata are identical implies that the location of the block is...
## Overview The inclusion of cryptographic-strength hash functions as checksum algorithms suggests that (some) users want maximum protection of filesystem metadata against manipulation. The current support for key-less/unseeded hash functions...
The table of contents on http://www.jqplot.com/examples/ does not contain the string "box" suggesting that data visualisation with box plots is missing in jqPlot. Ideally, jqPlot should offer drawing full box-and-whisker...
Add paragraph to readme explaining f3probe assumption and ask for reports on drives with different behaviour
Adding diagnostic output to `write_blocks()` and also simply looking at an I/O monitor, there clearly is a lot of data being written to the flash disk while running `f3probe`. The...
The "real limbo drive" unit test cases suggest an intention to detect wrapping by modulus other than a power of 2. However, the code `offset &= fdev->address_mask;` in `fdev_write_block()` that...
My brief inspections of the code suggest that f3probe assumes sector wrapping with a modulus that is a power of 2. Is this correct? It would be great to add...