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
Check Out this Related Man Page
XBDBACK(4) BSD/xen Kernel Interfaces Manual XBDBACK(4)NAME
xbdback -- Xen backend paravirtualized block device interface
SYNOPSIS
pseudo-device xbdback
DESCRIPTION
The xbdback interface forms the backend part of the paravirtualized drivers used by Xen domains to offer a block device interface, similar to
a hard disk. xbdback interfaces are backed either by a physical device directly, or an image file mounted through vnd(4).
All xbdback interfaces follow the ``xbdbackXiY'' naming convention, where 'X' represents the guest domain identifier, and 'Y' an arbitrary
identifier. This identifier is usually associated to the device node as seen by the guest using major(3) and minor(3) numbers. For example,
identifier ``769'' (0x301) means major 3 and minor 1, identified as ``hda1'' under Linux convention. For NetBSD, the guest device name spec-
ified in the guest configuration file does not matter, and can be chosen arbitrarily.
A xbdback interface will appear as a xbd(4) block device inside a NetBSD guest domain. In the XenStore, xbd and xbdback are identified by
``vbd'' (virtual block device) entries.
DIAGNOSTICS
xbd backend: attach device %s (size %d) for domain %d Gives the device used as xbdback interface for the given guest domain, and its size,
in bytes.
xbd backend 0x%x for domain %d using event channel %d, protocol %s Gives the backend identifier, guest domain ID, event channel ID, and pro-
tocol used for block level communication.
xbdback %s: can't VOP_OPEN device 0x%x: %d When this message appears in the system message buffer with error 16 (EBUSY), the device is
likely to be already mounted. It must be unmounted first, as the system will refuse to open it a second time.
SEE ALSO vnd(4), xbd(4), xenbus(4)HISTORY
The xbdback driver first appeared in NetBSD 4.0.
AUTHORS
The xbdback driver was written by Manuel Bouyer <bouyer@NetBSD.org>.
BSD June 7, 2011 BSD
I'm sure this is an easy one to answer - how do I turn a directory into a disk image of the sort that is mountable via mount -o loop?
I've been playing with comressed ram disk images on floppies
(dd if=/dev/fd0 of=disk1.img.gz; gzip -d disk1.img), and it seems that when i mount them and alter... (1 Reply)
Hi all,
I hope I'm putting my first post at this site into the right forum. I need help finding the EMC disk driver for AIX version 5.3. I have some new EMC disk presented to a backup server of mine, and right now the EMC hdisks show up looking like this in an lsdev:
hdisk495 Available... (2 Replies)
I was following this tutorial on How install the rpmfusion nvidia drivers in Fedora 13:
F13, F12 & F11 Nvidia driver guides - FedoraForum.org
Here's the tutorial:
And this is what I did:
First I executed the following commands:
su
rpm -Uvh ... (0 Replies)
Hello friends,
I am building one driver related to wifi. When I am looking its hex dump, I can see that it is including a path to one particular file of kernel headers. It is as under.
6C 75 65 2E 0A 00 00 00 25 64 2E 25 64 2E 25 64 lue.....%d.%d.%d
2D 25 73 00 00 00 00 00 42 45... (4 Replies)
Hi, I will try to keep my post as compressed as my title was.
I am writing on pseudo code on a recursive function that I want to read from the one-above function-run and then give the result to the function-run down below until a stop is triggered. Example:
$ ls -la | grep x | sort
In my... (2 Replies)
Hello Team,
Our p740 systems are booting up from SAN. We would like to configure the local disk(which is not part of rootvg) as a primary dump device. I have assigned the same too. But in the errpt throwing the below error. Please help me on this.
... (1 Reply)
Hi Everybody:
I'm searching a compressed Filesystem for a external disk, what I use for a full, diary and differential Backup.
The performance is not important, I search the best option for compress data, but I want have access to structure disk, with directories and files in the Backup disk.... (6 Replies)