Skip to content

Document LVM striped volume type deprecation #1111

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
WebberHuang1118 wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Document LVM striped volume type deprecation #1111

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 21 additions & 2 deletions docs/advanced/addons/lvm-local-storage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ You can only use one type of local volume in each volume group. If necessary, cr

![](/img/v1.4/csi-driver-lvm/create-lvm-sc-03.png)

- **Volume Group Type**: Select the type of local volume that matches your requirements. Harvester currently supports **striped** and **dm-thin**.
- **Volume Group Type**: Select **dm-thin**. This is the supported volume type for the LVM CSI driver.

![](/img/v1.4/csi-driver-lvm/create-lvm-sc-04.png)

Expand All @@ -106,6 +106,25 @@ You can only use one type of local volume in each volume group. If necessary, cr

For more information, see [StorageClass](../storageclass.md).

## dm-thin and Striped Volume Types

**dm-thin** is the supported volume type for the LVM CSI driver. Use **dm-thin** for all new volume groups and StorageClasses.

The **striped** volume type was available before the LVM CSI driver reached general availability, but is deprecated and is not included in the GA support scope. Striped logical volumes allocate their full capacity when they are created. Snapshots, clones, and restores also require full data copies, which consume additional capacity and I/O and can cause timeouts. Retrying an interrupted copy can also make it difficult to determine whether the operation completed successfully.

@jillian-maroket jillian-maroket Sep 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The **striped** volume type was available before the LVM CSI driver reached general availability, but is deprecated and is not included in the GA support scope. Striped logical volumes allocate their full capacity when they are created. Snapshots, clones, and restores also require full data copies, which consume additional capacity and I/O and can cause timeouts. Retrying an interrupted copy can also make it difficult to determine whether the operation completed successfully.
The **striped** volume type, which was available prior to the LVM CSI driver reaching general availability (GA), is deprecated and excluded from the GA support scope. Unlike thin-provisioned volumes, striped logical volumes allocate their full capacity upon creation. Operations such as snapshots, clones, and restores require full data copies, consuming additional storage capacity and I/O while increasing the risk of timeouts. Furthermore, retrying an interrupted copy operation can obscure whether the process completed successfully.


:::caution

Do not create new striped volume groups or StorageClasses. Existing striped volumes are not supported for GA and cannot be converted to dm-thin in place.

Before upgrading to a version that removes striped-volume support, migrate data from existing striped volumes:

1. Create a dm-thin volume group and StorageClass. A volume group can contain only one local volume type, so use a different volume group from the existing striped configuration.
1. Stop or quiesce the workload to prevent changes while its data is copied.
1. Create replacement volumes with the dm-thin StorageClass, and migrate the data using the workload's supported backup, restore, or copy procedure.
1. Update the workload to use the replacement volumes and verify the data before removing the striped volumes and StorageClass.
Comment on lines +119 to +124

@jillian-maroket jillian-maroket Sep 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Before upgrading to a version that removes striped-volume support, migrate data from existing striped volumes:
1. Create a dm-thin volume group and StorageClass. A volume group can contain only one local volume type, so use a different volume group from the existing striped configuration.
1. Stop or quiesce the workload to prevent changes while its data is copied.
1. Create replacement volumes with the dm-thin StorageClass, and migrate the data using the workload's supported backup, restore, or copy procedure.
1. Update the workload to use the replacement volumes and verify the data before removing the striped volumes and StorageClass.
Before upgrading to a Harvester version that removes support for this volume type, migrate data from existing striped volumes:
1. Create a new dm-thin volume group and StorageClass (separate from the existing striped configuration).
1. Stop or quiesce the workload to prevent data changes during the migration process.
1. Create replacement volumes using the new dm-thin StorageClass, then migrate the data using the workload's supported backup, restore, or copy procedure.
1. Update the workload to use the replacement volumes and verify data integrity before deleting the original striped volumes and StorageClass.


:::

## Creating a Volume with LVM

1. On the Harvester UI, go to the **Volumes** screen.
Expand Down Expand Up @@ -177,4 +196,4 @@ You can also create a new virtual machine with the volume of the LVM StorageClas

Backup creation is currently not supported. This limitation will be addressed in a future release.

:::
:::
6 changes: 4 additions & 2 deletions docs/advanced/csidriver.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,7 @@ The following is an example of an LVM storage profile:
apiVersion: cdi.kubevirt.io/v1beta1
kind: StorageProfile
metadata:
name: lvm-node-1-striped
name: lvm-node-1-dm-thin
spec:
claimPropertySets:
- accessModes:
Expand All @@ -165,11 +165,13 @@ status:
dataImportCronSourceFormat: pvc
provisioner: lvm.driver.harvesterhci.io
snapshotClass: lvm-snapshot
storageClass: lvm-node-1-striped
storageClass: lvm-node-1-dm-thin
```

For more information, see [Storage Profiles](https://github.com/kubevirt/containerized-data-importer/blob/main/doc/storageprofile.md) in the CDI documentation.

For LVM storage, use a dm-thin StorageClass. The striped volume type is deprecated and is outside the LVM CSI GA support scope. For more information, see [dm-thin and Striped Volume Types](./addons/lvm-local-storage.md#dm-thin-and-striped-volume-types).

@jillian-maroket jillian-maroket Sep 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For LVM storage, use a dm-thin StorageClass. The striped volume type is deprecated and is outside the LVM CSI GA support scope. For more information, see [dm-thin and Striped Volume Types](./addons/lvm-local-storage.md#dm-thin-and-striped-volume-types).
You must use a dm-thin StorageClass for LVM storage. The striped volume type is deprecated and excluded from the LVM CSI general availability (GA) support scope. For more information, see [dm-thin and Striped Volume Types](./addons/lvm-local-storage.md#dm-thin-and-striped-volume-types).


You can define the above fields to override the default configuration showing on the status.

:::caution
Expand Down
Loading