Engineering utility · local processing

Linux LUN, LVM and mount planner

Build a fail-closed, distribution-neutral runbook for one dedicated multipath LUN, a new LVM stack, and a persistent XFS or ext4 mount.

Privacy: Entries remain in this browser tab. The utility does not transmit, persist, or place infrastructure values in URLs.

Approved storage design

Target FQDN or hostnameStable mapper pathMust be under /dev/mapper; dm-N paths are rejected.Expected WWID16-128 hexadecimal characters. Runtime identity must match mpath-WWID exactly.Expected LUN size (GiB)FilesystemNew VG nameNew thick LV nameExplicit LV size (GiB)Minimum reserve (GiB)New mount pathThe path must not already exist; this prevents hidden writes beneath an unmounted filesystem.OwnerGroupDirectory modeDependent systemd service (optional)Adds RequiresMountsFor without enabling or starting the service.

Destructive-output gate

All generated artifacts remain hidden until every statement is confirmed. Any design input change relocks this gate.

The WWID and stable mapper path were independently verified against the storage assignment.This is a dedicated, blank, whole-device LUN presented to one host only; no partitioning or shared/clustered LVM is intended.The new PV, new VG, one thick LV, explicit reserve, filesystem, and mount design has peer approval.I understand creation is destructive, scripts must run as root in a change window, and rollback is never automatic.

Type CREATE vg_appdata/lv_appdata ON

Baseline: systemd, multipath-tools, lvm2, util-linux, and xfsprogs or e2fsprogs. This planner intentionally excludes existing data, partitions, shared LUNs, clustered LVM, thin provisioning, multiple LVs, force flags, wiping, and automatic rollback.

Operator artifacts

Attest to the approved design and enter the exact confirmation phrase to generate scripts. Nothing is sent or saved.