Block I/O support


driver [blk option[,option…]] [fstype [options]]

Runs on:

QNX Neutrino


The driver is one of the devb-* drivers, such as devb-eide, and option is one of the options described below.

The optional fstype argument is one of the filesystem drivers (fs-*); you can follow it with options specific to the filesystem.

Suffixes for size, memory, and time arguments

You can use suffixes on the arguments to some options to specify the units. These suffixes aren't case-sensitive.

For size arguments, the suffixes are:

For memory arguments, the suffixes also include:

For time arguments, the suffixes are:

blk options

You can specify the following options only in the blk section:

Set the cache/memory allocation policy to one of the following:
  • cache — allocate all of the buffer cache (the cache=size) at startup, but allocate all other caches (e.g., names) on demand and let them grow to their specified limit, and then start removing the Least Recently Used (LRU) items.
  • demand — allocate the buffer cache the same way, on-demand (it will grow from 0 to the size specified by the cache option as you access the disk).
  • upfront — pregrow all caches to their full size. This option can be useful in RAM-tuning a system, to see how much memory the filesystem will eventually consume (things such as the name and vnode caches tend to grow over time).

The default is cache.

Set the amount of automounting to be performed; amount is one of:
  • none — only raw block devices appear.
  • partition — enumerate any partition tables.

The default is partition.

Create a mountpoint for dev at mountpoint. If you don't specify a full path for the device, uses the value of its devdir option as a prefix. For example, if devdir is /dev (the default), an option of automount=hd0t177:/disk mounts /dev/hd0t177 at /disk.

The optional ptype specifies the partition type for a partitioned medium (e.g, hard disk, SD card), and must be one of dos, mac, nt, or qnx6.

The optional fstype specifies the filesystem type, and may be followed by filesystem options; if you don't specify fstype, the library tries to determine the filesystem automatically. The choices of filesystem and the associated shared objects are:

qnx6 (Power-Safe filesystem)

To mount multiple filesystems on a (removable) device, specify that the device is shared with a + prefix. For example:


For a list of common partition types, see the Filesystems chapter of the System Architecture guide.

The automounts are as specified in the given file. The file is a list of mounts (using the same syntax as above), separated by newline characters or commas.
Note: You can't locate the filename file in the filesystem to be automounted: it has to be available in an existing filesystem such as the image filesystem. Optionally, you could locate it in any devb filesystem that's already running.
Specify the total size of the disk buffer cache. The buffer cache is used as intermediate storage for all disk I/O, as well as providing LRU caching for dirty delayed-write blocks and recently-read blocks.

By default, 2 MB plus 2% of system RAM is assigned, with a maximum of 512 MB. If you specify an explicit size, bounds of 512 KB and 3 GB are applied.

Normally this cache is allocated at startup; if you specify alloc=demand, or the initial allocation failed, then the cache is dynamically grown as required up to the specified size.

The optional hash argument specifies the size of the buffer cache hash list. You can specify any of the suffixes described above. The default is 25% of the number of entries in the cache.

  • The default cache size is excessive for devb-ram. You'll probably want to reduce it to the minimum:
    devb-ram blk cache=512k &
  • By default in QNX Neutrino 6.5 and later, allocates the filesystem buffer cache (blk cache=) on affected ARM platforms from a global memory region (SHMCTL_ANON | SHMCTL_GLOBAL) to avoid the per-process 32 MB limitation. To override this and make the allocation from the normal devb-* process heap, specify blk memory=sysram.
(QNX Neutrino 7.0 or later) Allocate contiguous physical memory for the block cache (the majority of's memory). This speeds up I/O by eliminating virtual-to-physical translation later. The default is yes.
Specify the delay time for write-behinds to the media. A dirty disk block may remain in the cache without being physically written to the disk, to improve performance. The default is up to 3 seconds (delay1) for fixed media, and 1 second (delay2) for removable media. For more information, see Controlling writing operations,” below.

The postpone argument specifies the number of seconds for which to keep a dirty disk block in memory if it's being continuously modified, before physically writing it to the disk. This applies only to fixed media; for removable media, writes aren't delayed beyond the delay2 period. By default, postpone is the same as delay1.

The directory in which io-blk presents the physical devices as block-special files. The default is /dev.
Controls how major device numbers are requested; type is one of:
  • name — use the name of the device (e.g., hd, cd).
  • class — use the CAM class of the device (e.g., direct, readonly).
  • common — use a single class for all block devices.

The default is name.

(QNX Neutrino 7.0 or later) Specifies the rules for performing the DCMD_FSYS_DIRECT_IO devctl() command, disallowing it completely, or allowing it for read-only, write-only, or read-write operations. The default is rw.
Set the order for enumerating disk partitions; one of the following:
  • forward — enumerate slots 1 through 4, followed by any extended partitions.
  • reverse — enumerate slots 4 through 1, followed by any extended partitions.
  • windows — enumerate the active partition, followed by any extended partitions, and then non-booting primary partitions. For more information about this order, see

The default is forward.

Require/obtain exclusive access of the mount device. This means that when a filesystem is mounted on a partition, nothing else is allowed to open that raw partition until the filesystem is unmounted.
Specify the storing of open file names for the iofdinfo() query. The options for mode are:
  • ncache — try to reconstruct the file name from the contents of the directory name cache. Don't rely on this option to supply the names of all open files (a file's name is supplied only if all components of its pathname are in the name cache).
  • always — store the name used in each open() call to ensure that this name is always available.
  • never — never supply the name of an open file.

The default is always.

(QNX Neutrino 7.0 or later) Force all's threads that handle I/O to run at the given priority. The default is for them to inherit priorities.
(QNX Neutrino 6.6 or later) Set the filesystem event manager name. The default is defined by FSE_DEFAULT_MANAGER_NAME in <sys/fs_events.h> and is currently /dev/fsevents.
(QNX Neutrino 6.6 or later) Set the the maximum period of time to delay before sending events to the event manager. The default is defined by FSE_DEFAULT_PERIOD_MS in <sys/fs_events.h> and is currently 250 ms.
(QNX Neutrino 6.6 or later) Set the size of the event buffer, in kilobytes. The default is defined by FSE_DEFAULT_BUFFER_SIZE in <sys/fs_events.h> and is currently 50 KB.
Set the number of entries in a cache used to map translations from logical blocks to physical ones. If this option isn't specified, the size is based in the value of the vnode option.

The hash argument specifies the size of the associated hash list; the default is 1/6 of the number of entries in the map.

(QNX Neutrino 6.6 or later) Set the maximum allowed I/O, between vnode locks. You can use this option to break up I/O requests to improve reduce the latency of transactions during long I/O operations. The default is 2m:2m.
Limit the size of I/O requests that composes and hands over to the library. This option is expressed in terms of disk sectors; the default is 128 disk sectors, or 64 KB. The minimum setting is 32 disk sectors (16 KB). The maximum setting depends on the CPU:
  • For 32-bit CPUs, the maximum setting is 2040 sectors.
  • For 64-bit CPUs, it's 1352 sectors.

You should specify a power of two for num (e.g., 256, 512, or 1024 sectors, for 128 KB, 256 KB, or 512 KB respectively).

Note: This option simply caps the size of I/O requests that composes; it doesn't actually force to build large I/O requests.
Specify the typed memory pool or pools to use. For example, memory=sysram&below4G:sysram says to try sysram with the below4G modifier, and if no such region exists, then try plain sysram. (The same option works on systems with more or less than 4 GB of RAM.)
  • It's up to the startup to set up typed memory. Use pidin syspage=asinfo to see the list.
  • Generally you don't need to specify the memory option, in which case uses the normal mmap() pool; but on a system with more than 4 GB of RAM, it's mandatory.
  • You might have to quote this option, in order to prevent the shell from interpreting special characters such as an ampersand (&).

For more information about typed memory, see Typed memory in the Interprocess Communication (IPC) chapter of the System Architecture guide.

Specify the MFU:MRU segmentation (typically as a percentage, but it can be a size). You can specify any of the suffixes described above. The default is a 50:50 split.

The first time a sector is accessed, it goes into the MRU (Most Recently Used) region; if it's accessed again, it goes into the MFU (Most Frequently Used). The oldest cache blocks are removed from either the MRU or MFU region, so as to preserve this ratio.

Set the device/partition naming scheme. The default is 0#0. For more information, see Naming schemes,” below.
Specify a name cache of size entries. Using more name cache entries speeds up path/file lookups at the expense of memory. Setting the size to 0 disables name caching. If this option isn't specified, the size is determined from the vnode option.

The hash argument specifies the size of the associated hash list; the default is 1/6 of the size of the number of entries in the name cache.

(QNX Neutrino 6.6 or later) Specify whether or not the DCMD_FSYS_PREGROW_FILE devctl() command (see the Devctl and Ioctl Commands reference) zeroes the content when growing files. Zeroing the content is the default but increases the time for pregrowing files; not zeroing is very fast but insecure, as it allows access to the old content of the disk blocks.
Set the priority of periodic filesystem callouts. The default is 21.
Set the minimum and maximum sizes of the read-ahead buffers. You can specify any of the suffixes described above. The default minimum is the system page size; the default maximum is 64 times the system page size.
Create an internal ramdisk device (/dev/ramX) of the specified size, with the specified sector size. The size and sector variables can use the suffixes described above. The sector size must be power of 2 in the range from 512 through 4096 bytes; the default is 512 bytes.

If you specify the physical address (paddr), the contiguous physical memory starting at that location is mapped in and is unaltered for use. The physical address should be aligned to the system page size. You can use this argument to “reload” a RAM filesystem.

Note: If you don't specify paddr, the initial contents of this memory device are unspecified, so you must format it before using it as a filesystem (for example, with mkqnx6fs for a Power-Safe filesystem).
Choose the read-ahead policy. Read ahead means the speculative prefetching of the contents of files when the disk cache has good reasons to believe that the user will request these contents soon. Fetching the file contents in advance allows the subsequent read() to find the data already resident in the disk cache, so this system call won't need to generate an I/O request to bring this data in from disk and then wait for the disk I/O to complete.
  • traditional — this policy aims to strike a balance between the expected benefits of read-ahead and its potential costs (reading blocks that the client won't request later on). It's a good choice for memory-constrained systems, or systems where files are accessed in a predominantly random manner.
  • aggressive — this policy assumes that a file will be accessed in large chunks in a sequential manner, and that read() calls will come in a rapid sequence. It's therefore beneficial to load as many of the file's subsequent blocks into page cache as possible in anticipation that the client will request them very soon. This is a speculative bet; if the client doesn't behave as expected, there's a higher volume of disk I/O, and space is wasted in the page cache. This policy is a good choice for multimedia systems with a sizable disk cache.

The default is traditional.

The polling period for removable media. The default is 0 seconds.
Specify a removable media timeout (default: 2 seconds). After the specified period of inactivity, a disk access prompts validation of the media with the driver; if the driver reports that the media has been changed, all data blocks and cached information for that device are discarded and relearned.

This option can take a value of none, which disables removable media relearning. This isn't very useful for real removable devices (e.g., CDs), but if your device is on-board SD, or USB that isn't removable but the driver is advertising it as such, you can disable the verification overheads.

Specify the delay in milliseconds before sending a free-space notification. When the amount of free space on a drive changes, a filesystem event (fse) notification is sent from In case the free space is fluctuating rapidly, this option makes delay before delivering the event. The value must be in the range from 100 ms through 10000 ms. The default is 1000 ms.
(QNX Neutrino 7.0 or later) Set the stack size for all threads. The size must be in the range from 20 KB through 100 KB; the default is 20k.
Set the thread pool parameters (maximum, low water, and high water). The default is 12:2:5.
Be verbose. The output is sent to the system logger, slogger2.

The optional level argument is a series of alphabetic characters that indicates the categories of event to log:

  • b — bad blocks
  • c — configuration
  • d — direct I/O
  • f — fsys module (fs-*)
  • i — input
  • o — output
  • r — removable
  • v — virtual filesystem (VFS)

An option of blk verbose means all (bcdfiorv), blk verbose=io means input plus output, blk verbose=!r means everything except removable, and so on. The default is none.

Specify the number of vnode entries (filesystem-independent inodes) The default is 1024 entries. Up to size vnodes may be active. Vnodes remain in this cache when the corresponding file is closed, making subsequent opens faster.

The max argument allows a momentary large number files to be open at the same time; the cache tries to stay at size entries, but grows if needed up to max entries before giving an error of ENFILE. The default value of max is 3 times size.

Filesystem options

You can apply the following options globally (in the blk section) or to a specific filesystem:

Mount the filesystem so that it's resolved after any other filesystems mounted at the same pathname (in other words, it's placed behind any existing mount). When you access a file, the system looks on this filesystem last, and only if the file wasn't found on any other filesystems.
Mount the filesystem so that it's resolved before any other filesystems mounted at the same pathname (in other words, it's placed in front of any existing mount). When you access a file, the system looks on this filesystem first.
Set the committing level of the filesystem, which controls how dirty system/user blocks are written to disk. The level is one of none, low, medium (the default), and high. If it's none, all writes are time-delayed (as specified by the delwri option); at high, all writes are performed synchronously. For more information, see Controlling writing operations,” below.
Set the action to perform when a fs-* filesystem module detects an internal error. The action is one of:
  • ebadfsys — simply return EBADFSYS to the client.
  • mountro — return EBADFSYS to the client and remount the affected filesystem as read-only.

The default is ebadfsys.

Set the filesystem-dirty marking behavior. The mode must be none or mount (the default). If marking is on, the filesystem is marked as being dirty when it's mounted, and it's marked as being clean when it's unmounted. The method of marking depends on the filesystem.
(QNX Neutrino 6.6 or later) Specify the group ID to use for the mountpoint.
(QNX Neutrino 6.6 or later) Specify the permissions to use for the mountpoint. For more information about octal permission values, see the entry for chmod.

If you specify this as a global blk option, it causes the device special files (/dev/hd0, /dev/hd0tXXX, etc.) to have the specified file access permissions. It also causes the filesystem mountpoint to have the same permissions. If you use it in a specific filesystem section, then only filesystems of that type are affected.

(QNX Neutrino 6.6 or later) Specify the user ID to use for the mountpoint.
Note: You can also specify the mnt* options via the -o option to mount. If you do, the options given to the specific mount override those provided on the driver command line. For example:
# devb-eide cam blk cache=10m,mntperms=0741,mntuid=32,mntgid=709
# ls -l /dev/hd0*
total 13784609
brwxr----x 1 32 709 5, 0 Jan 18 02:44 hd0
brwxr----x 1 32 709 1, 9 Jan 18 02:44 hd0t177

# mount -t qnx6 -omntperms=0555,mntuid=600,mntgid=1034 /dev/hd0t177 /fs/qnx6
# ls -ld /fs/qnx6
dr-xr-xr-x 6 600 1034 8192 Jan 18 02:41 /fs/qnx6
Update/don't update the file's directory entry if the only change is the access time. The noatime option isn't strict POSIX 1003.2 behavior, but it's faster.
Allow/don't allow files to be created on this filesystem.
Allow/don't allow file execution from this filesystem.
Lock/don't lock removable media. If locked, the medium is treated as fixed.
Don't/do allow invalid mounts on removable media (re-insert).
Ignore/don't ignore the set-user ID bit on files in this filesystem.
Mount all drives/filesystems as read-only.
Mount all drives/filesystems as read-write (if the physical media permit). This is the default.

For more information about the before and after options, see Pathname Management in the Process Manager chapter of the System Architecture guide.


The library provides block I/O support, as used by the devb-*, drivers, and loads filesystem drivers (fs-*) as necessary.

The default values of the map and ncache options are based on the value of the vnode option. This arrangement lets you configure a system by specifying the cache size and the number of files, and letting the library set the other options.

Controlling writing operations

There are various types of writing operations:

Synchronous (SYNC)
Start immediately and wait for completion.
Asynchronous (ASYNC)
Start immediately but don't wait for completion.
Delayed (DELWRI)
Don't start until after a timeout period and then perform as asynchronous. The blk delwri= option controls the timeout for the delayed format; if you set this option to 0, a delayed writing operation is the same as asynchronous.
As required
Write only if you have to.

The types of data include:

What you read() and write().
Things associated with stat(), such as times and IDs.
Things such as bitmaps, extents, etc.

If a file has no links, the “as required” form of write operation is used, never going to disk unless the buffer or cache is needed (since the file has no links, the data isn't expected to be accessible after a power failure). If you open a file with O_SYNC, the synchronous format is always used.

Otherwise, the blk commit level controls the type of write to use for each level of data:

commit= Filesystem data Metadata User data
If you specify commit=none, you lose all write ordering (both for single multiblock updates and multiple-user operations). Hence, your chances of a useful recovery following a power failure are poor. We recommend that you use this option only if you have a uninterruptible power supply (UPS).

Calling close() might force a metadata update, but does nothing to the user data. Calling fsync() always forces out any delayed-write blocks for the file, and so is useful only when commit isn't high.

Naming schemes

You can use the naming=scheme option to specify the naming scheme to use for devices and partitions. The scheme must be a string of at least two characters; the default is 0#0.

The first two characters govern the naming of the raw disk and MBR partitions, as follows:

Character 1 Character 2 Naming scheme
A digit # The raw devices are numbered from the given digit, and MBR partitions are named from the device with a t followed by the OS type of the partition (see Partitions in the Filesystems chapter of the System Architecture guide). For example, a Power-Safe partition could be named hd0t177.

For duplicate partitions, a period (.) and sequence number are appended (e.g., hd0t12, hd0t12.1, and hd0t12.2 for logical/extended DOS partitions). This is the QNX Neutrino naming scheme.

A digit A lowercase letter The raw devices are numbered from the given digit, and MBR partitions are named starting with the given letter (e.g., /dev/hd0, /dev/hd0a, /dev/hd0b, /dev/hd0c, and so on). The name doesn't indicate the OS type of the partitions, just the order in which they were found.
A lowercase letter A digit The raw devices are named starting with the given letter. Primary MBR partitions are named 1, 2, 3, and 4; if you don't have four of them, the unused numbers are skipped. Any extended partitions are numbered without gaps from 5 (e.g., /dev/hda, /dev/hda1, /dev/hda2, /dev/hda5, and so on).

The name doesn't indicate the OS type of the partition, just its location. This is the Linux naming scheme.

A GPT partition has the following properties:

The name that gives to a GPT partition is in the form /dev/disk_name.partition_type.identifier. If recognizes the GUID for the partition type, it uses the alias as partition_type; otherwise it uses the GUID. The third character of the naming scheme governs the identifier as follows:

Character 3 identifier
A digit The sum of the given digit and the slot in the GPT table that defines the partition
@ The descriptive string for the partition.
Any other character The GUID that's unique to the partition
Change to a different naming scheme at your own risk:
  • Some system components could have hard-coded assumptions about disk names.
  • Don't use a different scheme unless you're in control of the entire system.
  • If you use a different scheme, you'll need some external knowledge about what filesystem to mount on a partition, because you won't have the tXXX naming hint.

This library includes the character sets for Japanese, traditional Chinese, and standard Chinese (code pages 932, 936, and 950); loads this library if it needs to mount a FAT volume, CD, or DVD that's formatted in one of these locales.