-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
rhel-10.1
-
None
-
No
-
None
-
rhel-storage-management
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
Did the libblockdev support to get luks status after it suspended ?
from cryptsetup cmd get the suspended in mode field
Running: 'cryptsetup -v status suspend_io_test'... /dev/mapper/suspend_io_test is active. type: LUKS2 cipher: aes-xts-plain64 keysize: 512 [bits] key location: dm-crypt device: /dev/mapper/npo2linear sector size: 4096 [bytes] offset: 32768 [512-byte units] (134217728 [bytes]) size: 12550144 [512-byte units] (51405389824 [bytes]) mode: read/write (suspended) Command successful.
Running: 'dmsetup info suspend_io_test'... Name: suspend_io_test State: SUSPENDED Read Ahead: 256 Tables present: LIVE Open count: 0 Event number: 0 Major, minor: 253, 4 Number of targets: 1 UUID: CRYPT-LUKS2-7f380f4297314e46b82a6996e155636b-suspend_io_test
# 1. libblockdev API try: api_status = luks_helper.bd.crypto_luks_status(mapped_device) print(f" - libblockdev API: {api_status}") except Exception as e: print(f" - libblockdev API: error {e}")
libblockdev API: active
libblockdev-3.2.0-5.el10.x86_64
6.12.0-119.el10.x86_64
