Differential D31926 Diff 95469 documentation/content/en/articles/vinum/_index.adoc

Changeset View

Standalone View

documentation/content/en/articles/vinum/_index.adoc

Context not available.
	:sectnumlevels: 6	:sectnumlevels: 6
	:source-highlighter: rouge	:source-highlighter: rouge
	:experimental:	:experimental:
		:images-path: articles/vinum/

	ifeval::["{backend}" == "html5"]	ifdef::env-beastie+backend-html5[]
	include::shared/en/urls.adoc[]	include::shared/authors.adoc[]
	:imagesdir: ../../../images/articles/vinum/	include::shared/mirrors.adoc[]
	endif::[]	include::shared/releases.adoc[]
		include::shared/{{% lang %}}/mailing-lists.adoc[]
	ifeval::["{backend}" == "pdf"]	include::shared/{{% lang %}}/urls.adoc[]
	include::../../../../shared/en/urls.adoc[]	:imagesdir: ../../../images/{images-path}
	:imagesdir: ../../../../static/images/articles/vinum/
	endif::[]	endif::[]

	ifeval::["{backend}" == "epub3"]	ifndef::env-beastie[]
	:imagesdir: ../../../../static/images/articles/vinum/	include::../../../../shared/asciidoctor.adoc[]
	endif::[]	endif::[]

	'''	'''
Context not available.

	[NOTE]	[NOTE]
	====	====
	Starting with FreeBSD 5, [.filename]#vinum# has been rewritten in order to fit into the link:{handbook}#geom[GEOM architecture], while retaining the original ideas, terminology, and on-disk metadata.	Starting with FreeBSD 5, [.filename]#vinum# has been rewritten in order to fit into the extref:{handbook}[GEOM architecture, geom], while retaining the original ideas, terminology, and on-disk metadata.
	This rewrite is called _gvinum_ (for _GEOM vinum_).	This rewrite is called _gvinum_ (for _GEOM vinum_).
	While this chapter uses the term [.filename]#vinum#, any command invocations should be performed with `gvinum`.	While this chapter uses the term [.filename]#vinum#, any command invocations should be performed with `gvinum`.
	The name of the kernel module has changed from the original [.filename]#vinum.ko# to [.filename]#geom_vinum.ko#, and all device nodes reside under [.filename]#/dev/gvinum# instead of [.filename]#/dev/vinum#.	The name of the kernel module has changed from the original [.filename]#vinum.ko# to [.filename]#geom_vinum.ko#, and all device nodes reside under [.filename]#/dev/gvinum# instead of [.filename]#/dev/vinum#.
Context not available.
	==== Only Primary Bootstrap Loads	==== Only Primary Bootstrap Loads

	If [.filename]#/boot/loader# fails to load, but the primary bootstrap still loads (visible by a single dash in the left column of the screen right after the boot process starts), an attempt can be made to interrupt the primary bootstrap by pressing kbd:[space].	If [.filename]#/boot/loader# fails to load, but the primary bootstrap still loads (visible by a single dash in the left column of the screen right after the boot process starts), an attempt can be made to interrupt the primary bootstrap by pressing kbd:[space].
	This will make the bootstrap stop in link:{handbook}#boot-boot1[stage two].	This will make the bootstrap stop in extref:{handbook}[stage two, boot-boot1].
	An attempt can be made here to boot off an alternate partition, like the partition containing the previous root file system that has been moved away from `a`.	An attempt can be made here to boot off an alternate partition, like the partition containing the previous root file system that has been moved away from `a`.

	[[vinum-root-panic]]	[[vinum-root-panic]]
Context not available.
	However, the stage one and two bootstraps plus the bsdlabel require 8 KB.	However, the stage one and two bootstraps plus the bsdlabel require 8 KB.
	So if a [.filename]#vinum# partition was started at offset 0 within a slice or disk that was meant to be bootable, the [.filename]#vinum# setup will trash the bootstrap.	So if a [.filename]#vinum# partition was started at offset 0 within a slice or disk that was meant to be bootable, the [.filename]#vinum# setup will trash the bootstrap.

	Similarly, if the above situation has been recovered, by booting from a "Fixit" media, and the bootstrap has been re-installed using `bsdlabel -B` as described in link:{handbook}#boot-boot1[stage two], the bootstrap will trash the [.filename]#vinum# header, and [.filename]#vinum# will no longer find its disk(s).	Similarly, if the above situation has been recovered, by booting from a "Fixit" media, and the bootstrap has been re-installed using `bsdlabel -B` as described in extref:{handbook}[stage two, boot-boot1], the bootstrap will trash the [.filename]#vinum# header, and [.filename]#vinum# will no longer find its disk(s).
	Though no actual [.filename]#vinum# configuration data or data in [.filename]#vinum# volumes will be trashed, and it would be possible to recover all the data by entering exactly the same [.filename]#vinum# configuration data again, the situation is hard to fix.	Though no actual [.filename]#vinum# configuration data or data in [.filename]#vinum# volumes will be trashed, and it would be possible to recover all the data by entering exactly the same [.filename]#vinum# configuration data again, the situation is hard to fix.
	It is necessary to move the entire [.filename]#vinum# partition by at least 4 KB, in order to have the [.filename]#vinum# header and the system bootstrap no longer collide.	It is necessary to move the entire [.filename]#vinum# partition by at least 4 KB, in order to have the [.filename]#vinum# header and the system bootstrap no longer collide.
Context not available.