vnd(4) [netbsd man page]

VND(4)							   BSD Kernel Interfaces Manual 						    VND(4)

NAME

     vnd -- vnode disk driver

SYNOPSIS

     pseudo-device vnd
     options VND_COMPRESSION

DESCRIPTION

     The vnd driver provides a disk-like interface to a file.  This is useful for a variety of applications, including swap files and building
     miniroot or floppy disk images.

     This document assumes that you're familiar with how to generate kernels, how to properly configure disks and pseudo-devices in a kernel con-
     figuration file.

     In order to compile in support for the vnd, you must add a line similar to the following to your kernel configuration file:

	   pseudo-device  vnd	    # vnode disk driver

     To also compile in support for reading compressed disk images, add the following option to your kernel config file:

	   options	  VND_COMPRESSION    # compressed vnd(4)

     Compressed disk images are expected in the cloop2 format, they can be created from "normal" disk images by the vndcompress(1) program.

     There is a run-time utility that is used for configuring both compressed and uncompressed vnds.  See vnconfig(8) for more information.

FILES

     /dev/{,r}vnd*  vnd device special files.

SEE ALSO

     config(1), vndcompress(1), MAKEDEV(8), fsck(8), mount(8), newfs(8), vnconfig(8)

HISTORY

     The vnode disk driver was originally written at the University of Utah.  The compression handling is based on code by Cliff Wright
     <cliff@snipe444.org>.

BUGS

     The vnd driver does not work if the file does not reside in a local filesystem.

     The vnd driver does not work if the file is sparse.

BSD
								 December 18, 2009							       BSD

CCD(4)							   BSD Kernel Interfaces Manual 						    CCD(4)

NAME

     ccd -- Concatenated disk driver

SYNOPSIS

     pseudo-device ccd [count]

DESCRIPTION

     The ccd driver provides the capability of combining one or more disks/partitions into one virtual disk.

     This document assumes that you're familiar with how to generate kernels, how to properly configure disks and pseudo-devices in a kernel con-
     figuration file, and how to partition disks.

     Note that the 'raw' partitions of the disks must not be combined.	Each component partition should be offset at least one cylinder from the
     beginning of the component disk.  This avoids potential conflicts between the component disk's disklabel and the ccd's disklabel.	The kernel
     will only allow component partitions of type FS_CCD.  But for now, it allows partition of all types since some port lacks support of an on-
     disk BSD disklabel.  The partition of FS_UNUSED may be rejected because device driver of component disk will refuse it.

     In order to compile in support for the ccd, you must add a line similar to the following to your kernel configuration file:

	   pseudo-device  ccd  4    # concatenated disk devices

     The count argument is how many ccds memory is allocated for at boot time.	In this example, no more than 4 ccds may be configured.

     A ccd may be either serially concatenated or interleaved.	To serially concatenate the partitions, specify the interleave factor of 0.

     If a ccd is interleaved correctly, a ``striping'' effect is achieved, which can increase performance.  Since the interleave factor is
     expressed in units of DEV_BSIZE, one must account for sector sizes other than DEV_BSIZE in order to calculate the correct interleave.  The
     kernel will not allow an interleave factor less than the size of the largest component sector divided by DEV_BSIZE.

     Note that best performance is achieved if all component disks have the same geometry and size.  Optimum striping cannot occur with different
     disk types.

     Also note that the total size of concatenated disk may vary depending on the interleave factor even if the exact same components are concate-
     nated.  And an old on-disk disklabel may be read after interleave factor change.  As a result, the disklabel may contain wrong partition
     geometry and will cause an error when doing I/O near the end of concatenated disk.

     There is a run-time utility that is used for configuring ccds.  See ccdconfig(8) for more information.

WARNINGS

     If just one (or more) of the disks in a non-mirrored ccd fails, the entire file system will be lost.

FILES

     /dev/{,r}ccd*  ccd device special files.

SEE ALSO

     config(1), MAKEDEV(8), ccdconfig(8), fsck(8), mount(8), newfs(8)

HISTORY

     The concatenated disk driver was originally written at the University of Utah.

BSD
								   March 5, 2004							       BSD