Skip to content

Tags: bor/f3

Tags

v5.0

Toggle v5.0's commit message
f3probe: avoid hanging before the second reset

f3probe was writing too many blocks between
the first and the second reset due to
a poor estimate of the writing and reseting times.

v4.0

Toggle v4.0's commit message
Bump next version to 4.0

Given that support for FreeBSD was added,
the next release will no longer be 3.1, but 4.0.

v3.0

Toggle v3.0's commit message
f3read: fix for Windows/Cygwin

Windows requires that the file descriptor passed to fdatasync(2)
to be writable.

Tom Hall reported the issue and proposed the solution.

v2.2

Toggle v2.2's commit message
Increment version to 2.2

v2.1

Toggle v2.1's commit message
Report version and copyright in help message

This was added mainly to help users to identify
the version they have installed.

v2.0

Toggle v2.0's commit message
Added a very simple Makefile

v1.1.3

Toggle v1.1.3's commit message
Version 1.1.3

Fixed some warning issued by GCC when compiling f3read.c on 64bits machines.
Nicolai Abruzzese was the first one to report this issue.
The outputs that he obtained were as follows:

f3read.c: In function 'report':
f3read.c:126: warning: format '%llu' expects type 'long long unsigned int', but argument 5 has type 'uint64_t'
f3read.c: In function 'iterate_path':
f3read.c:166: warning: format '%llu' expects type 'long long unsigned int', but argument 2 has type 'uint64_t'
f3read.c:166: warning: format '%llu' expects type 'long long unsigned int', but argument 3 has type 'uint64_t'
f3read.c:166: warning: format '%llu' expects type 'long long unsigned int', but argument 4 has type 'uint64_t'
f3read.c:166: warning: format '%llu' expects type 'long long unsigned int', but argument 5 has type 'uint64_t'

v1.1.2

Toggle v1.1.2's commit message
Version 1.1.2

Handled an I/O error reported by Misha Aizatulin.
The outputs that he obtained were as follows:

$ ./f3write /media/disk/
Free space: 122.01 GB
Creating file 0001.fff ... OK!
...
Creating file 0113.fff ... OK!
Creating file 0114.fff ... OK!
Creating file 0115.fff ... OK!
Creating file 0116.fff ... OK!
Creating file 0117.fff ... OK!
Free space: 0.00 Byte
Writing speed: 5.96 MB/s

$ ./f3read /media/disk/
                     SECTORS ok/corrupted/changed/overwritten
Validating file 0001.fff ... 0/0/0/2097152
Validating file 0002.fff ... 33280/0/0/2063872
Validating file 0003.fff ... 0/0/0/32 - NOT fully read
Validating file 0004.fff ... 0/0/0/2097152
Validating file 0005.fff ... 0/0/0/24192 - NOT fully read
Validating file 0006.fff ... 0/0/0/32 - NOT fully read
Validating file 0007.fff ... 0/0/0/32 - NOT fully read
...
Validating file 0035.fff ... 0/0/0/121984 - NOT fully read
Validating file 0036.fff ... 0/0/0/121984 - NOT fully read
Validating file 0037.fff ... 0/0/0/32 - NOT fully read
Validating file 0038.fff ... 0/0/0/32 - NOT fully read
...
Validating file 0113.fff ... 0/2097152/0/0
Validating file 0114.fff ... 0/2097152/0/0
Validating file 0115.fff ... 161888/1935264/0/0
Validating file 0116.fff ... 1980224/96768/0/20160
Validating file 0117.fff ... 265824/52416/0/0

  Data OK: 14.44 GB (30275959 sectors)
Data LOST: 13.77 GB (28874473 sectors)
               Corrupted: 9.92 GB (20793321 sectors)
        Slightly changed: 0.00 Byte (0 sectors)
             Overwritten: 3.85 GB (8081152 sectors)
WARNING: Not all data was read due to I/O error(s)
Reading speed: 15.77 MB/s

v1.1.1

Toggle v1.1.1's commit message
Version 1.1.1

Fixed some warnings issued by gcc when the parameter -Wall is
used to compile the source.

v1.1

Toggle v1.1's commit message
Version 1.1

- Added a nice report at the end of the output of f3read.
- Fixed bug on large memory cards.