NVM drives are fast enough to overflow 32-bit measurement variables
in bytes and blocks. This patch upgrades these variables to 64 bits.
This patch addresses issue #117:
https://github.com/AltraMayor/f3/issues/117
The file system HFS (i.e. "OS X Extended (Journaled)") of
macOS 10.11 may return a number of partial write()'s before
the file system is full.
This POSIX-permited, but unusual behavior was frist reported here:
https://github.com/AltraMayor/f3/issues/111
According to issue #102, calls to fdatasync() might take
a long time (.e.g. 3s or 4s) and distort the measurement of
the average write speed. This patch addresses it by only updating
the measurements when delays are within a tolerance.
Commit 7ff9fad37a32 ("libdevs: fix compiler warning") fixed the warning
by removing duplicate ‘const’ specifier.
The original intent of two ‘const’ specifiers, was most likely to make
non-mutable both: the ‘ftype_to_name‘ array itself and its elements,
so bring back the second ‘const’, but in the correct place this time,
i.e. after ‘*‘.
The comment explains from where the name B-RE-W comes.
It is meant to address some confusion that may raise as
the following pull request points out:
https://github.com/AltraMayor/f3/pull/96
Several of the HTTP links are now available over HTTPS, and the
documentation should link directly to the secure version of the
referenced page.
Along the way, a couple of broken links were updated.
The previous pull request broken Makefile for Linux.
It'd be great to have a solution for all platforms, but, for now,
one has to uncomment lines on Makefile to work on some platforms.
When measure() fails at the very last end of a file,
@remaining is zero.
Since @saved_errno is not ENOSPC, but @remaining is zero,
the code was considering that the file was properly written.
This parameter is useful to test cards that overheat.
Daniel Otero (@danielotero) pointed out the overheat problem, and
suggested the parameter as a solution in the following issue:
https://github.com/AltraMayor/f3/issues/37