V-Com Partition Commander 6.04 serial key or number

New Feature: Flex Capacity

Manage Your SSD

Monitor Drive Health

Get the Latest Firmware

Command-Line Interface

Download Storage Executive

1.6.1. Windows¶

On Windows, Cygwin (https://www.cygwin.com/) is required in order to build fio. To create an MSI installer package install WiX from https://wixtoolset.org and run from the directory.

How to compile fio on 64-bit Windows:

1. Install Cygwin (http://www.cygwin.com/). Install make and all packages starting with mingw64-x86_64. Ensure mingw64-x86_64-zlib are installed if you wish to enable fio’s log compression functionality.
2. Open the Cygwin Terminal.
3. Go to the fio directory (source files).
4. Run .

To build fio for 32-bit Windows, ensure the -i686 versions of the previously mentioned -x86_64 packages are installed and run before . To build an fio that supports versions of Windows below Windows 7/Windows Server 2008 R2 also add to the end of the configure line that you run before doing .

It’s recommended that once built or installed, fio be run in a Command Prompt or other ‘native’ console such as console2, since there are known to be display and signal issues when running it under a Cygwin shell (see https://github.com/mintty/mintty/issues/56 and https://github.com/mintty/mintty/wiki/Tips#inputoutput-interaction-with-alien-programs for details).

1.6.2. Documentation¶

Fio uses Sphinx to generate documentation from the reStructuredText files. To build HTML formatted documentation run and direct your browser to . To build manual page run and then . To see what other output formats are supported run .

1.11.1. Environment variables¶

Fio also supports environment variable expansion in job files. Any sub-string of the form as part of an option value (in other words, on the right of the ‘=’), will be expanded to the value of the environment variable called VARNAME. If no such environment variable is defined, or VARNAME is the empty string, the empty string will be substituted.

As an example, let’s look at a sample fio invocation and job file:

This will expand to the following equivalent job file at runtime:

Fio ships with a few example job files, you can also look there for inspiration.

1.11.2. Reserved keywords¶

Additionally, fio has a set of reserved keywords that will be replaced internally with the appropriate value. Those keywords are:

$pagesize

The architecture page size of the running system.

$mb_memory

Megabytes of total memory in the system.

$ncpus

Number of online available CPUs.

These can be used on the command line or in the job file, and will be automatically substituted with the current system values when the job is run. Simple math is also supported on these keywords, so you can perform actions like:

and get that properly expanded to 8 times the size of memory in the machine.

1.12.1. Parameter types¶

str

String: A sequence of alphanumeric characters.

time

Integer with possible time suffix. Without a unit value is interpreted as seconds unless otherwise specified. Accepts a suffix of ‘d’ for days, ‘h’ for hours, ‘m’ for minutes, ‘s’ for seconds, ‘ms’ (or ‘msec’) for milliseconds and ‘us’ (or ‘usec’) for microseconds. For example, use 10m for 10 minutes.

int

Integer. A whole number value, which may contain an integer prefix and an integer suffix:

[integer prefix] number [integer suffix]

The optional integer prefix specifies the number’s base. The default is decimal. 0x specifies hexadecimal.

The optional integer suffix specifies the number’s units, and includes an optional unit prefix and an optional unit. For quantities of data, the default unit is bytes. For quantities of time, the default unit is seconds unless otherwise specified.

With =1000, fio follows international standards for unit prefixes. To specify power-of-10 decimal values defined in the International System of Units (SI):

• K – means kilo (K) or 1000
• M – means mega (M) or 1000**2
• G – means giga (G) or 1000**3
• T – means tera (T) or 1000**4
• P – means peta (P) or 1000**5

To specify power-of-2 binary values defined in IEC 80000-13:

• Ki – means kibi (Ki) or 1024
• Mi – means mebi (Mi) or 1024**2
• Gi – means gibi (Gi) or 1024**3
• Ti – means tebi (Ti) or 1024**4
• Pi – means pebi (Pi) or 1024**5

With =1024 (the default), the unit prefixes are opposite from those specified in the SI and IEC 80000-13 standards to provide compatibility with old scripts. For example, 4k means 4096.

For quantities of data, an optional unit of ‘B’ may be included (e.g., ‘kB’ is the same as ‘k’).

The integer suffix is not case sensitive (e.g., m/mi mean mebi/mega, not milli). ‘b’ and ‘B’ both mean byte, not bit.

Examples with =1000:

• 4 KiB: 4096, 4096b, 4096B, 4ki, 4kib, 4kiB, 4Ki, 4KiB
• 1 MiB: 1048576, 1mi, 1024ki
• 1 MB: 1000000, 1m, 1000k
• 1 TiB: 1099511627776, 1ti, 1024gi, 1048576mi
• 1 TB: 1000000000, 1t, 1000m, 1000000k

Examples with =1024 (default):

• 4 KiB: 4096, 4096b, 4096B, 4k, 4kb, 4kB, 4K, 4KB
• 1 MiB: 1048576, 1m, 1024k
• 1 MB: 1000000, 1mi, 1000ki
• 1 TiB: 1099511627776, 1t, 1024g, 1048576m
• 1 TB: 1000000000, 1ti, 1000mi, 1000000ki

To specify times (units are not case sensitive):

• D – means days
• H – means hours
• M – means minutes
• s – or sec means seconds (default)
• ms – or msec means milliseconds
• us – or usec means microseconds

If the option accepts an upper and lower range, use a colon ‘:’ or minus ‘-‘ to separate such values. See irange. If the lower value specified happens to be larger than the upper value the two values are swapped.

bool

Boolean. Usually parsed as an integer, however only defined for true and false (1 and 0).

irange

Integer range with suffix. Allows value range to be given, such as 1024-4096. A colon may also be used as the separator, e.g. 1k:4k. If the option allows two sets of ranges, they can be specified with a ‘,’ or ‘/’ delimiter: 1k-4k/8k-32k. Also see int.

float_list

A list of floating point numbers, separated by a ‘:’ character.

With the above in mind, here follows the complete list of fio job parameters.

1.12.2. Units¶

¶

Select the interpretation of unit prefixes in input parameters.

1000

Inputs comply with IEC 80000-13 and the International System of Units (SI). Use:

• power-of-2 values with IEC prefixes (e.g., KiB)
• power-of-10 values with SI prefixes (e.g., kB)

1024

Compatibility mode (default). To avoid breaking old scripts:

• power-of-2 values with SI prefixes
• power-of-10 values with IEC prefixes

See for more details on input parameters.

Outputs always use correct prefixes. Most outputs include both side-by-side, like:

bw=2383.3kB/s(2327.4KiB/s)

If only one value is reported, then kb_base selects the one to use:

1000 – SI prefixes

1024 – IEC prefixes

¶

Base unit for reporting. Allowed values are:

0

Use auto-detection (default).

8

Byte based.

1

Bit based.

1.12.3. Job description¶

¶

ASCII name of the job. This may be used to override the name printed by fio for this job. Otherwise the job name is used. On the command line this parameter has the special purpose of also signaling the start of a new job.

¶

Text description of the job. Doesn’t do anything except dump this text description when this job is run. It’s not parsed.

¶

Run the specified number of iterations of this job. Used to repeat the same workload a given number of times. Defaults to 1.

¶

Create the specified number of clones of this job. Each clone of job is spawned as an independent thread or process. May be used to setup a larger number of threads/processes doing the same thing. Each thread is reported separately; to see statistics for all clones as a whole, use in conjunction with . See . Default: 1.

1.12.5. Target file/device¶

¶

Prefix filenames with this directory. Used to place files in a different location than . You can specify a number of directories by separating the names with a ‘:’ character. These directories will be assigned equally distributed to job clones created by as long as they are using generated filenames. If specific filename(s) are set fio will use the first listed directory, and thereby matching the filename semantic (which generates a file for each clone if not specified, but lets all clones use the same file if set).

See the option for information on how to escape “” characters within the directory path itself.

Note: To control the directory fio will use for internal state files use .

¶

Fio normally makes up a filename based on the job name, thread number, and file number (see ). If you want to share files between threads in a job or several jobs with fixed file paths, specify a filename for each of them to override the default. If the ioengine is file based, you can specify a number of files by separating the names with a ‘:’ colon. So if you wanted a job to open and as the two working files, you would use . This also means that whenever this option is specified, is ignored. The size of regular files specified by this option will be divided by number of files unless an explicit size is specified by .

Each colon in the wanted path must be escaped with a character. For instance, if the path is then you would use and if the path is then you would use .

On Windows, disk devices are accessed as for the first device, for the second etc. Note: Windows and FreeBSD prevent write access to areas of the disk containing in-use data (e.g. filesystems).

The filename “-” is a reserved name, meaning stdin or stdout. Which of the two depends on the read/write direction set.

¶

If sharing multiple files between jobs, it is usually necessary to have fio generate the exact names that you want. By default, fio will name a file based on the default file format specification of . With this option, that can be customized. Fio will recognize and replace the following keywords in this string:

$jobname

The name of the worker thread or process.

$jobnum

The incremental number of the worker thread or process.

$filenum

The incremental number of the file for that worker thread or process.

To have dependent jobs share a set of files, this option can be set to have fio generate filenames that are shared between the two. For instance, if is specified, file number 4 for any job will be named . The default of will be used if no other format specifier is given.

If you specify a path then the directories will be created up to the main directory for the file. So for example if you specify then the directories a/b/c will be created before the file setup part of the job. If you specify then the path will be relative that directory, otherwise it is treated as the absolute path.

¶

To avoid collisions between networked clients, fio defaults to prefixing any generated filenames (with a directory specified) with the source of the client connecting. To disable this behavior, set this option to 0.

¶

Recursively open any files below directory str.

¶

Fio defaults to not locking any files before it does I/O to them. If a file or file descriptor is shared, fio can serialize I/O to that file to make the end result consistent. This is usual for emulating real workloads that share files. The lock modes are:

none

No locking. The default.

exclusive

Only one thread or process may do I/O at a time, excluding all others.

readwrite

Read-write locking on the file. Many readers may access the file at the same time, but writes get exclusive access.

¶

Number of files to use for this job. Defaults to 1. The size of files will be divided by this unless explicit size is specified by . Files are created for each thread separately, and each file will have a file number within its name by default, as explained in section.

¶

Number of files to keep open at the same time. Defaults to the same as , can be set smaller to limit the number simultaneous opens.

¶

Defines how fio decides which file from a job to service next. The following types are defined:

random

Choose a file at random.

roundrobin

Round robin over opened files. This is the default.

sequential

Finish one file before moving on to the next. Multiple files can still be open depending on .

zipf

Use a Zipf distribution to decide what file to access.

pareto

Use a Pareto distribution to decide what file to access.

normal

Use a Gaussian (normal) distribution to decide what file to access.

gauss

Alias for normal.

For random, roundrobin, and sequential, a postfix can be appended to tell fio how many I/Os to issue before switching to a new file. For example, specifying would cause fio to issue 8 I/Os before selecting a new file at random. For the non-uniform distributions, a floating point postfix can be given to influence how the distribution is skewed. See for a description of how that would work.

¶

Attempt to switch the device hosting the file to the specified I/O scheduler before running.

¶

If true, serialize the file creation for the jobs. This may be handy to avoid interleaving of data files, which may greatly depend on the filesystem used and even the number of processors in the system. Default: true.

¶

fsync(2) the data file after creation. This is the default.

¶

If true, don’t pre-create files but allow the job’s open() to create a file when it’s time to do I/O. Default: false – pre-create all necessary files when the job starts.

¶

If true, fio will only run the setup phase of the job. If files need to be laid out or updated on disk, only that will be done – the actual job contents are not executed. Default: false.

¶

If true, fio is permitted to create files as part of its workload. If this option is false, then fio will error out if the files it needs to use don’t already exist. Default: true.

¶

If this isn’t set, fio will abort jobs that are destructive (e.g. that write) to what appears to be a mounted device or partition. This should help catch creating inadvertently destructive tests, not realizing that the test will destroy data on the mounted file system. Note that some platforms don’t allow writing against a mounted device regardless of this option. Default: false.

¶

If this is given, files will be pre-read into memory before starting the given I/O operation. This will also clear the flag, since it is pointless to pre-read and then drop the cache. This will only work for I/O engines that are seek-able, since they allow you to read the same data multiple times. Thus it will not work on non-seekable I/O engines (e.g. network, splice). Default: false.

¶

Unlink the job files when done. Not the default, as repeated runs of that job would then waste time recreating the file set again and again. Default: false.

¶

Unlink job files after each iteration or loop. Default: false.

¶

Accepted values are:

none

The , , :option zonecapacity and option:zoneskip parameters are ignored.

strided

I/O happens in a single zone until bytes have been transferred. After that number of bytes has been transferred processing of the next zone starts. :option zonecapacity is ignored.

zbd

Zoned block device mode. I/O happens sequentially in each zone, even if random I/O has been selected. Random I/O happens across all zones instead of being restricted to a single zone. The parameter is ignored. and must be identical.

¶

Size of a single zone. See also and .

¶

For =strided, this is the number of bytes to transfer before skipping bytes. If this parameter is smaller than then only a fraction of each zone with bytes will be accessed. If this parameter is larger than then each zone will be accessed multiple times before skipping to the next zone.

For =zbd, this is the size of a single zone. The parameter is ignored in this mode.

¶

For =zbd, this defines the capacity of a single zone, which is the accessible area starting from the zone start address. This parameter only applies when using =zbd in combination with regular block devices. If not specified it defaults to the zone size. If the target device is a zoned block device, the zone capacity is obtained from the device information and this option is ignored.

¶

For =strided, the number of bytes to skip after bytes of data have been transferred. This parameter must be zero for =zbd.

¶

This parameter applies to =zbd only.

Zoned block devices are block devices that consist of multiple zones. Each zone has a type, e.g. conventional or sequential. A conventional zone can be written at any offset that is a multiple of the block size. Sequential zones must be written sequentially. The position at which a write must occur is called the write pointer. A zoned block device can be either drive managed, host managed or host aware. For host managed devices the host must ensure that writes happen sequentially. Fio recognizes host managed devices and serializes writes to sequential zones for these devices.

If a read occurs in a sequential zone beyond the write pointer then the zoned block device will complete the read without reading any data from the storage medium. Since such reads lead to unrealistically high bandwidth and IOPS numbers fio only reads beyond the write pointer if explicitly told to do so. Default: false.

¶

When running a random write test across an entire drive many more zones will be open than in a typical application workload. Hence this command line option that allows to limit the number of open zones. The number of open zones is defined as the number of zones to which write commands are issued.

¶

A number between zero and one that indicates the ratio of logical blocks with data to the total number of logical blocks in the test above which zones should be reset periodically.

¶

A number between zero and one that indicates how often a zone reset should be issued if the zone reset threshold has been exceeded. A zone reset is submitted after each (1 / zone_reset_frequency) write requests. This and the previous parameter can be used to simulate garbage collection activity.

1.12.6. I/O type¶

¶

If value is true, use non-buffered I/O. This is usually O_DIRECT. Note that OpenBSD and ZFS on Solaris don’t support direct I/O. On Windows the synchronous ioengines don’t support direct I/O. Default: false.

¶

If value is true, attempt to use atomic direct I/O. Atomic writes are guaranteed to be stable once acknowledged by the operating system. Only Linux supports O_ATOMIC right now.

¶

If value is true, use buffered I/O. This is the opposite of the option. Defaults to true.

¶

Type of I/O pattern. Accepted values are:

read

Sequential reads.

write

Sequential writes.

trim

Sequential trims (Linux block devices and SCSI character devices only).

randread

Random reads.

randwrite

Random writes.

randtrim

Random trims (Linux block devices and SCSI character devices only).

rw,readwrite

Sequential mixed reads and writes.

randrw

Random mixed reads and writes.

trimwrite

Sequential trim+write sequences. Blocks will be trimmed first, then the same blocks will be written to.

Fio defaults to read if the option is not specified. For the mixed I/O types, the default is to split them 50/50. For certain types of I/O the result may still be skewed a bit, since the speed may be different.

It is possible to specify the number of I/Os to do before getting a new offset by appending to the end of the string given. For a random read, it would look like for passing in an offset modifier with a value of 8. If the suffix is used with a sequential I/O pattern, then the <nr> value specified will be added to the generated offset for each I/O turning sequential I/O into sequential I/O with holes. For instance, using will skip 4k for every write. Also see the option.

¶

If an offset modifier is given by appending a number to the line, then this option controls how that number modifies the I/O offset being generated. Accepted values are:

sequential

Generate sequential offset.

identical

Generate the same offset.

is only useful for random I/O, where fio would normally generate a new random offset for every I/O. If you append e.g. 8 to randread, you would get a new random offset for every 8 I/Os. The result would be a seek for only every 8 I/Os, instead of for every I/O. Use to specify that. As sequential I/O is already sequential, setting for that would not result in any differences. behaves in a similar fashion, except it sends the same offset 8 number of times before generating a new offset.

¶

Fio normally reports statistics on a per data direction basis, meaning that reads, writes, and trims are accounted and reported separately. If this option is set fio sums the results and report them as “mixed” instead.

¶