Skip to main content
NetApp Knowledge Base

Trident Misidentifies Filesystems on LUKS Devices Due to blkid

  1. Last updated
  2. Save as PDF
Views:
2
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
astra
Last Updated:

Applies to

  • NetApp Trident (all versions prior to 26.02, especially 25.10 and 25.06)
  • Kubernetes environments using Trident with LUKS-encrypted volumes
  • Linux hosts (blkid utility involved)

Issue

When provisioning LUKS-encrypted volumes with NetApp Trident, the filesystem on the underlying LUN is sometimes misidentified. This results in mount failures or incorrect filesystem reporting. The issue is seen sporadically and can block operations, causing delays and impacting productivity.

Example log output:

MountDevice failed for volume: rpc error: code=Internal desc=failed to stage volume: LUN trident_pvc-xxxxx, device dm-xx already formatted with other filesystem: atariblkid on the node also confirms this type: /dev/mapper/luks-trident_pvc_pvc-xxxxx: PTTYPE="atari"

Other misidentifications include jmicron_raid and random filesystems, especially when the underlying LUN is all zeros.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.