GEOM_LINUX_LVM(4) BSD Kernel Interfaces Manual GEOM_LINUX_LVM(4)NAME
geom_linux_lvm -- GEOM based Linux LVM logical volume mapping
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
options GEOM_LINUX_LVM
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
geom_linux_lvm_load="YES"
DESCRIPTION
The geom_linux_lvm framework provides support for mapping Linux LVM volumes to GEOM providers. geom_linux_lvm currently supports linear
stripes with segments on one or more physical disks. The parser is able to read LVM2 Text Format metadata, the logical volumes will be
assembled and made available under /dev/linux_lvm/. The metadata is read-only, logical volumes cannot be allocated or resized.
EXAMPLES
To view which geom_linux_lvm devices are available:
# geom linux_lvm list
Geom name: vg1
Providers:
1. Name: linux_lvm/vg1-home
Mediasize: 4294967296 (4.0G)
Sectorsize: 512
Mode: r0w0e0
2. Name: linux_lvm/vg1-logs
Mediasize: 4294967296 (4.0G)
Sectorsize: 512
Mode: r0w0e0
Consumers:
1. Name: ada0s1
Mediasize: 80023716864 (75G)
Sectorsize: 512
Mode: r0w0e0
SEE ALSO GEOM(4), geom(8)AUTHORS
The geom_linux_lvm driver was written by Andrew Thompson <thompsa@FreeBSD.org>.
BSD October 1, 2013 BSD
Check Out this Related Man Page
GEOM_UZIP(4) BSD Kernel Interfaces Manual GEOM_UZIP(4)NAME
geom_uzip -- GEOM based compressed disk images
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
options GEOM_UZIP
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
geom_uzip_load="YES"
DESCRIPTION
The geom_uzip framework provides support for compressed read only disk images. This allows significant storage savings at the expense of a
little CPU time on each read. Data written in the GEOM label area allows geom_uzip to detect compressed images which have been created with
mkuzip(8) and presented to the kernel as a logical disk device via md(4). geom_uzip creates a unique md#.uzip device for each image.
The geom_uzip device is subsequently used by the FreeBSD kernel to access the disk images. The geom_uzip driver does not allow write opera-
tions to the underlying disk image. To check which md(4) devices match a given geom_uzip device:
# geom uzip list
Geom name: md1.uzip
Providers:
1. Name: md1.uzip
Mediasize: 22003712 (21M)
Sectorsize: 512
Mode: r1w0e1
Consumers:
1. Name: md1
Mediasize: 9563648 (9.1M)
Sectorsize: 512
Mode: r1w0e1
SEE ALSO GEOM(4), md(4), geom(8), mkuzip(8)AUTHORS
The geom_uzip driver was written by Max Khon <fjoe@FreeBSD.org>. This manual page was written by Ceri Davies <ceri@FreeBSD.org>.
BSD October 9, 2006 BSD
What exactly happens when you boot HP-UX with the -lm flag?
We tried this the other night, with some wacky results...
We poked around, and found that / was mounted to /dev/rroot (I think... maybe it was just /dev/root). So, (still playing) we activated the volume group (lvchange -ay), and... (2 Replies)
Hi all i have queastion. Can anybody pease help me
what is user mode and kernel mode and the term "De-mountable volumes" means?
Thanks
Palash (2 Replies)
I am an experienced MS Windows user who has tried four different flavors of Linux: Mandriva, Centos, Debian, and Ubantu---each on a different PC. (I always used a dual-boot configuration with Grub and Win XP or Win 7). Each time, I encountered the following two problems:
While resuming from... (2 Replies)